Jul 23, 2013; Arlington, TX, USA; New York Yankees second baseman Brent Lillibridge (39) singles in the winning run during the ninth inning of the game against the Texas Rangers at Rangers Ballpark in Arlington. The Yankees won 5-4. Mandatory Credit: Tim Heitman-USA TODAY Sports

Brent Lillibridge has a hot bat

Texas Rangers second baseman Brent Lillibridge is making a good case he could be a guy the keep on their roster.  So far during spring training, Lillibridge has one of the hottest bats with a .571 batting average.  Also, if the Ranger do keep him, Lillibridge is a guy that could help the Rangers out with several positions such a shortstop or in the outfield.  Richard Durrett commented on how Lillibridge is looking so far during spring training during the Chicago White Sox game.

Career Stats

Over his 6 years in the majors he has a career batting line of 205/.267/.332/.599.  Just over the Mendoza line.  He has played in 358 games/784 plate appearances /708 at-bats and has collected 25 doubles and 19 home runs.

Spring Training stats

Spring training has just started and it is a small sample set, but Lillibridge has 7 at-bats with 4 hits.  He has collected 3 runs and has one home run.

Expectations:  Don’t expect Lillibridge to take Jurickson Profar spot anytime soon.  Brent Lillibridge could be a player though the Rangers use when they do need to come off the bench for injuries or to give others rest.  Especially if he is able to keep finding the ball like he has so far.  Now, we know that average will come down, hopefully he’ll be able to settle in the .250s, which would be good for him.  Lillibridge like several others in spring training are out there to prove they have the stuff to make it.  Back in 2012 he re-tooled his swing, it didn’t show in his stats.  Maybe this year will be different for him.  At least for now , he’s hot and exciting to watch.  Hopefully that will continue throughout spring training.

Next Rangers Game View full schedule »

Tags: Brent Lillibridge Texas Rangers

comments powered by Disqus