Skip to main content 

Owing to the width of most of the many data tables on this site, it is best viewed from a desktop computer. If you are on a mobile device (phone or tablet), you will obtain a better viewing experience by rotating your device a quarter-turn (to get the so-called “panorama” screen view).


The Owlcroft Baseball-Analysis Site




Baseball team and player performance examined realistically and accurately.
 Click here to email us. 



You are here:  Home  »  dailies  »  teams  »  individual  »  projected  »   this page
(Click on any image above to see it at full size.)
You are here:  Home  »  dailies  »  teams  »  individual  »  projected  »   this page
(Click on any image above to see it at full size.)

You are here:  Home  »  dailies  »  teams  »  individual  »  projected  »   this page
You are here:  Home  »  dailies  »  teams  »  individual  »  projected  »   this page
You can get a site directory by clicking on the “hamburger” icon () in the upper right of this page.
Or you can search this site with Google (standard Google-search rules apply).

Search term(s):



Blue Jays 2025 Projected Batting Performance


All raw data supplied courtesy of Baseball-Reference.com.
They do a wonderful job, and deserve your support.

2025 Blue Jays Projected Batting

Through games of Friday, 16 May 2025.
All results are from true, unadjusted data.

Explanation of the Table

The Table below shows two lines for each player and for the team as a whole: Actual and Projected. The Actual lines are just what it says: the actual stats for this season to date; the Projected lines want a little explanation.

The projecting has two steps. The first is simple: for each man, we calculate the ratio of his current-season-to-date Plate Appearances to his career Plate Appearances, then multiply all his career stats by that ratio to get what one might call his “raw” career-performance data pro-rated to his current-year number of Plate Appearances. So, as a hypothetical example, a man with 5,000 career PAs and 250 PAs this season would have a ratio of 250/5000, or .050; so, if he had, say, 1215 career Hits, his raw projected Hits number for this season would be 1215 x .05, or 61 (if the calculated number is fractional, as with 60.75, we round it off to the nearest whole number).

That much is simple and, we hope, clear. The second adjustment takes a little explaining. It derives from the fact that—for a team or for an individual man—the number of Plate Appearances that will be had for a given number of Outs made (which is to say “innings played”) depends exactly on the on-base percentage: the higher the on-base percentage, the more PAs the man or team will have in any given number of innings.

To clarify: imagine a team with an abysmal .250 on-base percentage; that number means that, on average, one man in four that they send to the plate will get on safely. The converse of that is that three men in four will make out. (For simplicity’s sake in this elementary example, we ignore outs made on the bases.) So, in an average inning, that team, to make the three outs that constitute an inning, will send 4 men to the plate. If we next imagine a team with an equally absurd .500 on-base percentage, only half its batters make an out: thus, to make the three outs that define an inning, they would have—again, on average—to send 6 men to the plate. So (as should be intuitively obvious anyway), for a given number of innings, a higher OBP means more PAs.

The consequence of that is that each man’s “raw”stat projections, which were based on his PAs for this season, are slightly inaccurate, because his—and the team’s—PAs would be different (perhaps higher, perhaps lower) from what they are if all the men were performing at their career rates. To correct for that, we calculate each man’s career "outs rate" (all Outs made per plate appearance, which does include outs made on the bases) and multiply it by his percentage of the team’s total Plate Appearances; we then sum up those outs rates to get a projected team Outs rate, and from that—holding Outs made (which, again, is just innings played) constant—we can reckon the projected team PA total. We can then adjust each projected stat line by the ratio of expected team PAs to actual PAs (which normally yields a number fairly close to, but not equalling,1.0), giving us the true projected stats for each man and for the team.

(For this season for this team’s batting, the adjustment factor, rounded to three decimal places—the actual calculations use many more decimals— is 0.996)

Incidentally, that last adjustment is the reason that even rookies, whose whole “career” is just the current season, can have “adjusted” lines that differ slightly from their actual data lines, and why the TOP numbers here may differ slightly from those on other pages here.

You can see the overall “win-capability” of the team (its wins projected from these team numbers and the corresponding team pitching numbers) at our “Projected Team-Performances” page.

The Table

Player (alphabetical by last name) G PA AB H 2B 3B HR TB BB SH SF HBP CI TOP
Bo Bichette, actual: 44 202 187 55 15 0 4 82 12 0 1 2 0 834
Bo Bichette, projected: 44 201 188 55 11 0 7 87 11 0 1 1 0 831
Vladimir Guerrero Jr., actual: 44 194 164 48 8 0 5 71 27 0 2 1 0 988
Vladimir Guerrero Jr., projected: 44 193 171 49 10 0 9 85 19 0 1 2 0 972
Anthony Santander, actual: 39 173 155 29 5 0 5 49 17 0 1 0 0 428
Anthony Santander, projected: 39 172 156 38 8 0 8 72 13 0 1 2 0 737
George Springer, actual: 41 160 133 36 10 1 5 63 24 0 1 0 2 970
George Springer, projected: 41 159 139 36 6 1 7 65 17 0 1 2 0 936
Andrés Giménez, actual: 36 143 128 25 5 0 3 39 10 0 1 4 0 522
Andrés Giménez, projected: 36 142 128 33 6 1 3 50 7 1 1 5 0 719
Alejandro Kirk, actual: 34 137 131 36 4 0 3 49 4 0 1 1 0 569
Alejandro Kirk, projected: 34 136 121 32 5 0 3 47 13 0 1 1 0 717
Player (alphabetical by last name) G PA AB H 2B 3B HR TB BB SH SF HBP CI TOP
Ernie Clement, actual: 42 126 117 31 7 0 1 41 5 2 2 0 0 483
Ernie Clement, projected: 42 125 118 30 5 1 2 42 5 1 1 1 0 549
Alan Roden, actual: 28 84 73 13 3 0 1 19 5 0 2 4 0 426
Alan Roden, projected: 28 84 73 13 3 0 1 19 5 0 2 4 0 403
Nathan Lukes, actual: 29 81 68 18 2 0 3 29 9 1 1 2 0 745
Nathan Lukes, projected: 29 81 68 18 3 1 2 28 9 1 2 1 0 766
Myles Straw, actual: 36 80 74 23 4 0 1 30 3 3 0 0 0 639
Myles Straw, projected: 36 80 71 18 3 0 0 22 7 1 1 0 0 573
Addison Barger, actual: 23 74 68 17 7 0 2 30 5 0 0 1 0 733
Addison Barger, projected: 23 74 68 14 4 0 2 25 5 0 0 0 0 492
Will Wagner, actual: 20 68 59 11 2 0 0 13 8 1 0 0 0 470
Will Wagner, projected: 20 68 62 16 4 0 1 22 5 0 0 0 0 633
Player (alphabetical by last name) G PA AB H 2B 3B HR TB BB SH SF HBP CI TOP
Daulton Varsho, actual: 12 49 44 10 1 0 6 29 3 0 2 0 0 1040
Daulton Varsho, projected: 12 49 44 10 2 0 2 18 4 0 0 0 0 633
Tyler Heineman, actual: 16 45 43 17 4 0 1 24 1 0 1 0 0 1560
Tyler Heineman, projected: 16 45 39 9 2 0 0 12 3 1 0 1 0 435
Jonatan Clase, actual: 6 22 21 2 1 0 0 3 0 1 0 0 0 24
Jonatan Clase, projected: 6 22 20 4 1 0 0 6 1 0 0 0 0 291
Davis Schneider, actual: 10 21 15 1 0 0 0 1 5 0 0 1 0 436
Davis Schneider, projected: 10 21 18 4 1 0 1 7 2 0 0 0 0 679
Michael Stefanic, actual: 2 5 5 2 0 0 0 2 0 0 0 0 0 1166
Michael Stefanic, projected: 2 5 4 1 0 0 0 1 0 0 0 0 0 190
Blue Jays, Actual: 44 1664 1485 374 78 1 40 574 138 8 15 16 2 186
Blue Jays, Projected: 44 1657 1488 380 74 4 48 608 126 5 12 20 0 193


Assorted Team Stats:
Stat Actual Projected
Batting Average: 0.252 0.255
Slugging Average: 0.387 0.409
Walks (per PA): 0.083 0.076
SOs (per PA): 0.196 0.185
On-Base Average: 0.319 0.320
Power Factor: 1.535 1.600
OPS: 0.706 0.728
Runs Expected from Actual Stats: 186
Runs Expected from Projected Stats: 193
Actual Runs Scored: 175

Return to the page top. ↑




  Advertisement:


  Advertisement:



Want detailed, careful, unhysterical analysis of the effects of “Performance-Enhancing Drugs” in baseball? Click here to visit the Steroids & Baseball web site.

All content copyright © 2002 - 2025 by The Owlcroft Company.

This web page is strictly compliant with the WHATWG (Web Hypertext Application Technology Working Group) HyperText Markup Language (HTML5) Protocol versionless “Living Standard” and the W3C (World Wide Web Consortium) Cascading Style Sheets (CSS3) Protocol v3  — because we care about interoperability. Click on the logos below to test us!



This page was last modified on Saturday, 17 May 2025, at 4:02 am Pacific Time.