PLAY'S · COMMUNITY · 13 OCT 2026
Players losing to Dragerion keep naming the same card, and it is not Dragerion
The daily survey counts decks. The people posting about losing to this one do not talk about the deck much at all — they name 神滅竜騎ネルガルザーク, a card inside it, and the two ways it arrives early. Meanwhile the deck lost the lead on 12 October, which is the sort of thing posts do not keep up with. One more thing got in the way of reading them: the current ranked season appears to be named after the same card.
The search this site uses returns a handful of posts and then stops. It can show what individual people wrote and never what share of players wrote it. Handles are not reproduced. Its window also moves: the 29 September post below had already dropped out of the results by the time this page was checked on the evening of 13 October, so each post here is recorded from the reading that found it.
What the chart did while these posts were being written
| Date | Games | Leading named deck | Its share | Dragerion |
|---|---|---|---|---|
| 9 Oct | 238 | Raid | 14.7% | 11.3 |
| 10 Oct | 222 | HADES Dragerion | 18.0% | 18.0 |
| 11 Oct | 262 | see below | 12.6% | 12.6 |
| 12 Oct | 169 | Cotton Zenith | 15.4% | 13.6 |
Read from the daily charts on 11, 12 and 13 October. The page on the lead change has the ten days before this.
11 October does not have a clean answer. Dragerion read 12.6% and the Baraghiara loop line also read 12.6% — on 262 games that is thirty-three games each. Count Baraghiara as one family, adding the Cabbage entry at 2.3%, and it reads 14.9% and is ahead. So Dragerion led outright on one day, shared the top on the next by one reading and lost it by the other, and was second on the third.
None of the posts below mention any of that. They are about playing against the deck, which is a different thing from how often it appears.
The card they name is not the one on the box
On 13 October a player posting their Minogami Cup record went 1–4 on the first day of STAGE2 and said they met 火水闇ドラゲリオン twice. Their description of why they lost names no part of the Dragerion card: it was a combo using the cip of 学校男 or 堕魔 ドゥポイズ to put 神滅竜騎ネルガルザーク out early, and they had, in their words, no answer to it at all.
On 9 October a different player wrote that HADESドラゲリオン and ネルガルザーク were the two absurd power cards keeping them playing. That is two posts, four days apart, putting the same second card beside the first.
The earliest post found is older than the deck’s climb. On 29 September, when it was reading in the low single digits, someone who had come back to the game after a long gap wrote that they were piloting HADESドラゲリオン and ended with a one-line question about how many of its cards are simply too much. The Japanese there can be read as "too strong" or as "too badly designed"; the post does not say which, and this site is not going to pick one.
One player set out how they try to beat it
Also on 13 October: finish the game early, or cast オリオティス・ジャッジ and win immediately afterwards with speed attackers. Their own summary of how that goes was that they basically lose. That is one player's account of their own matches and not a matchup finding.
Half the search results are not about the deck at all
Searching the deck's name turns up posts that have nothing to do with it, because the current ranked season appears to be called ハデスドラゲリオンCUP. Players write the phrase to say when they did something, not what they played with.
Three posts make that unmistakable, because each names a different deck in the same breath. On 4 October someone reached New Division Legend in the Cup with 青緑バラギアラ. On 12 October someone reached All Division Master in the Cup and wrote their deck out in brackets: 赤白レイド. On 10 October a third reached New Division Master in the Cup, writing that it was their first in 32弾ぶり — the first in thirty-two sets — and that they had come back to both the format and the lists from scratch. The deck they describe afterwards is Raid as well.
The practical point is unchanged, and now rests on the publisher rather than on inference: a keyword search on this deck’s name is contaminated for as long as the season runs, and any count built from one would be wrong. That is a further reason the posts here are described one by one rather than totalled.
The practical point stands either way: a keyword search on this deck's name is contaminated for as long as the season runs, and any count built from one would be wrong. That is a further reason the posts below are described one by one rather than totalled.
People are still picking it up
On 13 October someone wrote that this month's spending would go on building HADESドラゲリオン. On 11 October an All Division player wrote that they were reusing their New Division Cotton and Dragerion decks in that format, and wanted to build something that only exists there instead. Those are two people, and this site cannot say whether either is typical.
The name count was wrong, and in the more embarrassing direction
The page on the lead change said this site had recorded four names for this deck. A Minogami Cup opponent list posted on 12 October used a fifth, クローシスダピコハデス, which welds three of the others together — and chasing that one down turned up the real miss.
Players also call it クローシスダピコ, and this site had never recorded that at all. A search on that name alone returned posts dated 27 September and 5, 6, 8, 9, 10 and 12 October — spread across the whole period these pages have been covering, including one calling it the deck Raid exists to beat, and a top-four list from a community event. It is not a rare spelling. It is a name this site simply had not seen, while publishing two pages that counted the names.
That makes six forms recorded now, and the honest lesson is the one the next paragraph was already about.
The naming page is about what this does to anyone comparing two sources. A fifth variant does not change its argument; it is simply more of the same problem.
A bug report, and a notice that does not quite match it
On 7 October a player set out a sequence step by step: play 双炎祭壇 アポロヌス・パトス, then HADESドラゲリオン without placing it underneath, have the opponent play あたりポンの助 to shut off the Dragerion effect, take −9000 from it, and then have it tucked under the Patos — at which point, they wrote, it breaks endlessly.
This site cannot say whether they share a cause, whether the posted sequence still happens, or whether the publisher knows about it. What can be said is that the post is six days old and nothing matching it has appeared in the notice. The same pattern — players describing a fault before the notice names it — happened at the end of September.
What this page is not
It is not a count and it is not a poll. Eleven posts are eleven people, and three of those turned out to be about a ranked season rather than a deck. One post the same searches returned is left out as spam.
It can now. During the 12 October broadcast the publisher announced a seventh にじさんじ collaboration and named five members: リゼ・ヘルエスタ, 鈴原るる, 栞葉るり, 舞元啓介 and 石神のぞみ. The posts are people guessing which deck each of the five will be matched with, and one of the guesses for 鈴原るる is this one. The publisher has not said that the collaboration pairs anybody with a deck; that part is the posters’ assumption, and it is reported here as such.
Nothing here says the deck is strong or weak. The daily figures above say how often people met it, and they are already pointing somewhere else.
Sources
Player posts: public posts on X dated 29 September and 4, 7, 9, 10, 11, 12 and 13 October 2026, located by Japanese keyword search on 12 and 13 October, described rather than quoted at length. Handles are not reproduced. The ranked season name is players' usage and is not confirmed by any publisher page this site can reach.
Daily New Division encounter surveys for 9–12 October 2026 at beans-duelplays.com, read from the charts on 11, 12 and 13 October 2026.
The known-issues notice: the publisher's running page, as it stood on 13 October 2026, headed as updated 7 October.
Card and deck names are given in Japanese where this site has not confirmed an English name.
Corrections and questions
If something here is wrong, please say so — that is the most useful thing you can do with this page. Comments use GitHub, so you will need an account, and everything posted lives in this site's own repository rather than on a third-party service. No tracking, no ads.