As a baseball or softball team manager, you can generate a roster, keep team stats to share with players, maintain a schedule, and communicate with the team. You can send game invitations and quickly see who will attend.
Players can view team stats, schedules, RSVP to games, and leave comments. Coming soon: live game scoring and automatic box scores/scoresheets.
Check out the tutorial for a full rundown.
Yes! Once you add a new team with the manager tools, you’ll see a "Change Team" link at the top. This allows you to switch between teams on the site.
Check with your manager. Only the manager knows the correct URL for your team.
If you use the same email address for each team, you’ll be able to view information for all teams when you log in. To switch teams, click on "Change Team" in the top-right corner of the page.
There are a lot of numbers! When viewing team stats, hover over the stat names to get a quick explanation of the abbreviations.
Buckle your seat belts.
BaseRuns (BsR), developed by David Smyth, estimates the runs a team "should" have scored given their component stats. Tom M. Tango notes that BaseRuns models the run-scoring process more accurately than other estimators.
Designed for Major League Baseball, BaseRuns has the lowest error rate among major run estimators, and unlike other metrics, it’s accurate in any baseball setting, even Little League. When a solo home run is hit, BaseRuns predicts one run—other metrics often overestimate. BaseRuns, however, adapts to any level as it reflects the game’s general mechanics.
(from Wikipedia on BaseRuns)
BaseRuns adjusts based on the environment, making it suitable for baseball and softball at all levels. For example, in high-scoring games, singles can approach the value of home runs, while in low-scoring games, home runs hold more weight.
Context truly matters. If every batter hit a homer, each would be worth one run, as no one would be on base. In a world of only walks, each walk would also be worth one run.
(from FanGraphs on BaseRuns)
BaseRuns handles extreme performances accurately, unlike other estimators. Runs Created, for instance, can artificially inflate values for players with high on-base and slugging stats.
Runs Created’s formula (A*B)/C is flawed for estimating individual runs as it assumes a player’s stats interact with their own, inflating values for high OBP and SLG players. OPS adds on-base and advancement factors, which reduces accuracy.
(from Wikipedia on Runs Created)
In summary, Monkeystats uses BaseRuns because it provides a more accurate view of player value than OPS or Runs Created.
BaseRuns excludes R and RBI, as these are resultant, not component, stats. Clutch performance isn’t factored in.
For more details, check out the literature on BaseRuns and sabermetrics online.
The Player of the Game (POG) is awarded to the player with the highest BaseRuns (BsR) in a game, estimating their contribution to run production. While traditional stats like RBI are often used to recognize performances, BsR gives a broader view. Lacking play-by-play data, it’s impossible to assess each RBI’s impact or "clutch" moments. A stat like Win Probability Added (WPA) might offer more detail, but that requires play-by-play data.
In high-scoring games, singles and doubles gain value as players reach base, while creating outs has a larger negative effect. In low-scoring games, home runs carry more weight. The formula emphasizes that avoiding outs is key—outs are the primary obstacle to run production.
In case of a tie, the POG is awarded randomly, an issue planned for correction in a future version of Monkeystats.
My name is Jeff. I'm a recreational baseball and softball player, and I’ve long wanted a better way to manage team stats and schedules. Tired of driving to games only to find not enough players, and tired of unreadable stat spreadsheets, I built this site to centralize team management, communicate with players, ensure attendance, and make stats accessible.
All the cool domain names were taken! After running through animals, "Monkeystats" was the only one available. And hey, monkeys are cool. So I win.
The site is still in development, and certain pages involve heavy number-crunching, especially when displaying stats or leaderboards. I’m working on optimizing the code!
Got more questions? Send them!