누누와 윌럼프 with 벨베스

TankFighter

Fighter

subTitle

numAnalyzed

승률

37.8 %

kda

1.92

인기도

0.2 %

method.title

At MOBA Champion, we download the results of from millions of League of Legends matches directly from Riot Games each week. 누누와 윌럼프 has fought alongside 벨베스 in 217 recently played, ranked matches. By accumulating so much accurate data from the developers of League, we are completely sure that we can produce high quality, accurate builds to help 누누와 윌럼프 synergize with 벨베스. It is very rare for 누누와 윌럼프 to play alongside 벨베스 on the same team. This pairing has only occurred in approximately 0.2% of rounds with 누누와 윌럼프.

summary.title

Unfortunately, 누누와 윌럼프 does a terrible job of playing alongside 벨베스. Usually, he wins a dismal 37.8% of rounds the champions try and work together in. If you want to maximize your potential as 누누와 윌럼프 when playing with 벨베스 by figuring out how to better synergize your strategy with them, then review the complete build (with items, runes, summoner spells, and skills) below!

Recommended Builds

all - 패치 13.24

최고 승률

Matchup Specific

vs. ChampionW/R

counterTitle

아이템

첫 번째 아이템

원하는 시간

다음 항목

5 분

핵심 누누와 윌럼프 아이템

22분

선택 품목

Summoner Spells

스킬 오더

룬

guide.title

guide.playingAs

누누는 잡아먹기를 이용하여 공격로에서 원거리 공격형 적을 만나도 버틸 수 있습니다.

절대 영도 사용 시 적이 범위에서 벗어나려 하면 기술 사용을 중단할 수 있습니다.

절대 영도는 서로 방해 스킬을 다 쓸 때까지 기다렸다 사용하십시오. 팀 전투 시 바로 뛰어들지 말고 뒤에서 대기하십시오.

counterStatsTitle

winRate

37.8 %

winRate

62.2 %

4.7

< kills >

5.3

7.4

< deaths >

6.7

9.5

< assists >

11.1

1.04

< killingSprees >

1.18

< cs >

0.66

< dragons >

1.56

0.27

< inhibitors >

0.38

926

< physicalDamage >

1,077

12,761

< magicDamage >

13,358

823

< trueDamage >

840

14,510

< damageDealt >

15,276

29,318

< damageTaken >

36,969

9,528

< goldEarned >

10,814

1.1

< towers >

1.26

0.2

< barons >

0.4

12,445

< heal >

19,841

11,007

< xp >

12,772

< visionScore >

< wardsPlaced >

321

< ccTime >

459

summary.titleContinued

The 누누와 윌럼프 벨베스 synergy stats shown here demonstrate the areas of his gameplay that do better (or worse) when paired with 벨베스, compared to his overall stats. Significant differences are areas of focus that highlight how his gameplay changes when paired with this other champion.

Overall, 누누와 윌럼프 sees a large worsening in his KDA (ratio of kills and assists to deaths) when paired with 벨베스. His KDA decreased from NaN to NaN. This drop shows that 벨베스 helps 누누와 윌럼프 perform not as well in competitive League of Legends rounds. Yet, the small difference demonstrates that this performance change is not very impactful.

When 누누와 윌럼프 is paired with 벨베스, he observes a little decrease in his full damage output. This could demonstrate that 벨베스 does not support by providing cover for him to deal more damage or that their presence on the team also helps increase the match's duration. Similarly, when 누누와 윌럼프 is played together with 벨베스 on the same side, he usually scores many fewer killing sprees than when he plays on his own. This is contrasting evidence that he is worse when playing alongside 벨베스.

Additionally, when 누누와 윌럼프 plays with 벨베스 on the same side, he usually receives much less damage than when he fights alone. Taking not as much damage could indicate that 벨베스 does a decent job of covering 누누와 윌럼프 in team fights.

championDifferences.title

데미지 유형

누누와 윌럼프

벨베스

물리적 손상

마법 피해

고정

championDifferences.playStyle.title

누누와 윌럼프

벨베스

championDifferences.whoIsBetter

There is no one best ally for 누누와 윌럼프 that will 100% of the time be his best ally. Yet, overall, 벨베스 is a very bad teammate for 누누와 윌럼프. By playing on the same side as 누누와 윌럼프, they lowers their win rate by -9.7% to 37.8%. This clearly indicates that there is a terrible bond between 누누와 윌럼프 and 벨베스 that allows them to perform worse together than without each other.

벨베스 has a much greater difficulty compared to 누누와 윌럼프. That means 누누와 윌럼프 players should be careful when arranging 벨베스 comrades to fight alongside, as they will need a much greater level of skill to be able to fight well with you.

Playing together, 누누와 윌럼프 players should expect to witness an overall large increase in your team’s capability to deal magic damage. Combined, these champs can deal quite a lot of AP type damage.

Although, by pairing 누누와 윌럼프 and 벨베스 together, you will not be providing your other allies a great deal of AD. We recommend you include other champs on your team that nullifies this disparity in this pairing's capabilities.

Regardless of your 벨베스 ally's skill level, you should focus on maximizing your income, warding to avoid ambushes, and clearing objectives. If you follow these simple suggestions, you will do well, regardless.

matchups.title

additionalInformation.title

method.title2

method.text2

additionalInformation.resources

누누와 윌럼프 Build 벨베스 Build

additionalInformation.readMore

If you would like to learn all of the intricacies of 누누와 윌럼프 to work well with 벨베스 during both the early game and mid / late game phases of LoL games, you should continue reading to pick up a few extra lessons on this champion pairing. If you use the build and tips presented here, you will grow your win rate significantly.

The ideal items to prioritize in your 누누와 윌럼프 and 벨베스 synergy build include 기사의 맹세, 얼어붙은 심장, and 리안드리의 고통. When 누누와 윌럼프 combined at least these three items in his build, he performed a lot better when fighting alongside 벨베스 than with most other commonly used item sets. In fact, 누누와 윌럼프 had an average win rate of 37.8% when synergizing his build and playstyle to 벨베스 with this build.

To have the highest probability of vanquishing your oponents, 누누와 윌럼프 players should take the 어둠의 수확, 비열한 한 방, 사냥의 증표, 끈질긴 사냥꾼, 기민함, and 물 위를 걷는 자 runes from the 지배 and 마법 rune sets. Out of all the rune sets players chose for this champion pairing, this set of runes resulted in the best win rate. Moreover, these runes gave a 37.8% winrate overall.

By default, tips, statistics, and builds on how to pair 벨베스 with 누누와 윌럼프 are given for all ranked divisions. If you want to narrow the statistics and builds to a specific player tier, you should use the selection menu earlier on the page.