Observed layout · recorded with these units
BatoForge observations // team meta · daily
Pipskull + Rattleghast
Inspect a Batomon Showdown combination's common full teams, supporting units and battle results by Run Day.
Build notes
Opening Knockouts → resources or growth
Rattleghast Knocks Out adjacent allies at battle start. Nekoffin converts its Knockout into a Trinket; other recipients can evolve or gain stats.
How it works
- Place the intended recipient next to Rattleghast without Protect blocking its Knockout.
- Knocked-out units need revival before they can resume ordinary casts.
Getting started
Conditions to check
- Rattleghast's battle-start effect happens once. Reviving an ally does not repeat it; include a damage source to use the extra resources.
- Check the positions and triggers, then fill the remaining slots with damage, protection or support the core lacks.
- Ability reference: build 26170127. Shop locations use older records; the observed teams' game version is unknown.
Completed period Oct 27 16:00 – Oct 28 16:00 UTCpartial
4,135,850 observations · all modes/regions · includes repeats · game version unknownThe selected Ranked / All period contains 970,642 distinct team votes;16,242 are grouped under this combination in Team Meta. Full teams and supporting units use that group. Trainer and rank details include all teams carrying these units, including teams in other groups.
- Appearance share
- 1.67% 16,242 / 970,642 team votes in this mode and region
- Day-battle win rate
- 42.3% n=16,242 (6870W/9372L)
- Avg observed Run Day
- day 3.1 Average age of the recorded teams, not when this combination first formed.
Most-seen full teams
These examples use records from Day 4 onward; compositions also seen earlier are included. Counts group Batomon by species; forms and levels are unknown. Each example labels its positions as observed, estimated, or unavailable.
Observed layout · recorded with these units
Observed layout · recorded with these units
Common supporting units
Share of teams in this Team Meta group that carry each additional unit.
These details include all teams carrying this combination, including teams in other Team Meta groups. There are 24,629 carrying team votes in the selected mode, region and period. Position, Trainer and rank samples differ; each section lists its count.
Where the units sit
Positions 1–6 follow the displayed two-row, three-column board. Each percentage uses that unit's position samples, including repeated copies. These separate samples do not show which six positions occurred together.
Trainers behind it
22 listed Trainers, covering 21,703 of 24,629 carrying team votes. Each win rate uses that Trainer's battles; n is its total wins and losses. 2,926 carrying team votes have no available Trainer detail.
Ladder spread
Shares use the 24,629 team votes with a known rank. Each win rate uses that rank's battles.
Master MMR bands
Percentages use all 14,570 Master team votes;14,570 have recorded MMR. Teams without MMR stay in "MMR unknown."
Presence and results by run day
The longest cyan bar marks the Run Day with the most recorded teams in this group. Other bars are scaled to that day. Each label shows that day's wins and losses; smaller samples also show a 95% confidence lower bound.
- Day 144.6%won
- Day 247.6%won
- Day 342.8%won
- Day 438.5%won
- Day 535.4%won
- Day 636.3%won
- Day 731.6%won
- Day 836.1%won
- Day 938.9%won
- Day 1050.0%won
- Day 1166.7%won
- Day 130.0%won
- Day 160.0%won

