lil bean
You already have 10 favorites. Remove one first, then add this.
Clash Royale player lil bean (#LLPR0L0Y) has 3,030 trophies and 435 wins in total. Currently on 2 wins in a row. The current deck has an average elixir cost of 4.4. Recent battles: 4 wins and 5 losses.
- Trophies3,030
- Streak2 wins in a row
- King Tower Level11
- Best trophies3,030
- Wins435
- Losses402
- Three crown wins632
Note: The streak is counted from the most recent battles in the battle log below. Friendly battles and Boat Defense battles are not counted.
Current deck
Card collection
Note: Of the cards you own, 0% are at max level.
-
Common 0 / 27 at max level (0%)
-
Rare 0 / 27 at max level (0%)
-
Epic 0 / 27 at max level (0%)
-
Legendary 0 / 11 at max level (0%)
Recent performance
4W 5L in the last 9 battles
Strong against (win rate above your overall win rate when the opponent plays this card)
Weak against (win rate below your overall win rate when the opponent plays this card)
No card has a win rate below your overall win rate.
Note: Aggregated from the recent battle log. The number of battles returned by the API varies.
Note: Ranked by a confidence interval that accounts for sample size, so cards seen only once or twice do not top the list on a lucky streak.
Recent battles
-
Win Crowns (you/opponent) 1 - 0DetailsOpponent Thomas Vercingetorice2v2 Teammate: LiamResolvedor
-
Win Crowns (you/opponent) 3 - 2DetailsOpponent Vercingetorice Thomas2v2 Teammate: VTEX ALPHA
-
Loss Crowns (you/opponent) 0 - 1Details2v2 Teammate: Mami _rakip ...
-
Loss Crowns (you/opponent) 1 - 2DetailsOpponent Dara kevin_elpru2v2 Teammate: Nikan
-
Loss Crowns (you/opponent) 0 - 3DetailsOpponent قسا TheWraithxVN2v2 Teammate: ehsan.af
-
Loss Crowns (you/opponent) 0 - 3DetailsOpponent incómodo#¥ 상추2v2 Teammate: Ace
-
Win Crowns (you/opponent) 3 - 2Details2v2 Teammate: ImagineLosing
-
Loss Crowns (you/opponent) 0 - 1DetailsOpponent محمود کلانتری Dr2v2 Teammate: zaki
-
Win Crowns (you/opponent) 3 - 0DetailsOpponent EZrektbarbarian Avg. Lv.8.5Trophy Road
Note: The official API returns only the most recent battles. Neither the count nor paging can be specified.