let me know what you think of it, its not very formulated yet but whatever here it is OBP- 150- leader is 150 (player total/leader x 150) avg- 50- leader is 50 hr- 50- leader is 50 wRC- 200- leader is 200 (player total/leader x 200) sb- 15- leader is 15 sb %- 15 slg %- 150- leader is 150 ct %- 150- ct % x 150 war- 100-leader is 100 bb:so- 100- leader is 100 TB- 100- leader 100 wOBA- 200- leader 200 ISO- 100- leader 100 spd- 10 bsr- 10 (neg is 0) total points available- 1400 /13 TEMPLATE wOBA (200)- wRC (200)- OBP (150)- SLG (150)- CT (150)- WAR (100) TB (100)- BB:SO (100)- ISO (100)- AVG (50)- HR (50)- SB (15)- SB % (15)- SPD (10) BSR (10) TOTAL= /13 T-SKY RATING: The T-sky rating is my new baseball statistic that combines sabremetrics and some traditional baseball statistics. The idea is to combine many different statistics and try to get just one number that assess a player total value. The number is to be viewed out of 100. The maximum score a player can attain is 1400, this number is then divided by 13. While, this makes it possible for a hitter to attain a score of 112, it is nearly impossible. It is best to look at the player’s number as if it’s out of 100. The reason I don’t divide it by 14 so that the scale is 100, is because the values depend on the league leader and can therefore unfairly punish a player. For example, if a player has a legendary season with say a .490 OBP, and the second place finisher has a .430, the second place finisher’s score out of 200 would be just 175, and I think we can agree that if someone has a .430 OBP, there score should be higher than that. It makes it nearly impossible for a player to get a score higher than in the low 90s if I divided by 14. While, you can choose to just divide by 14 and accept results, or even choose a different number to divide by than 13, I just find that dividing by 13 is effective. So just remember, a player’s T-sky Rating should be viewed as if 100 is the best possible score one can achieve. It sounds like a lot, and it’s very complicated, but overall, it can be used as an accurate measure of how good a player really is. All values are rounded to the tenth spot Troy Tulowitzki as of 6/3/14 wOBA (200)- 200 wRC (200)- 197.9 OBP (150)- 150 SLG (150)-147.5 CT (150)- 120.9 WAR (100)- 100 TB (100)- 85.1 BB:SO (100)- 64.9 ISO (100)- 86.9 AVG (50)- 50 HR (50)- 35 SB (15)- .4 SB % (15)- 15 SPD (10)- 4.6 BSR (10)- 0 TOTAL= 1258.2 /13 T-SKY RATING: 96.8
would there be a way to bring a player's salary into it so u could determine how much value a team is or is not getting for a player?
Yup lol.... I use fangraphs to get the actual statistics but I created the formula on my own and input the data for each player on my own
Baseball Abstract move over.... a new kids in town...! I'm getting to old for this amount of data..... but, - good work....!
it wouldn't be a statistic involving salary, it would have to be some kind of ratio between my overall rating and the salary
also i have not done any ratings since Tulo a few weeks ago because I figured hed be tops then...I'd have to do this every day with every player to keep it consistent but I don't have the time for that
So how does base stealing and sb% combined equate to home runs? If you look at the statistical success of SB leading to run production, vs. the guaranteed run production by HR, I think either HR is under valued or SB is over valued. That was the first thing that jumped out at me.
dont look at it as hr vs. sb, look at his powerr vs baserunning. There's better indications of power than HR, ISO for example. Baserunning has just sb, sb%, spd, and bsr Power has hr, iso, slg, for more total points over 200 more So power is weighted significantly more heavily than baserunning
