Telegram RegisterThe public register of Telegram
Telegram profile photo for 北落野

Channel

北落野

@blywuwa31

On this record: Topic · Growth · Engagement · Posts · Polls · Cite this entry

5subscribers

+2 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1003706891368
TypeChannel
Username@blywuwa31
Created24 April 2026 — measured — dated from the channel’s first post
First recorded13 August 2026
Last confirmed live10 October 2026
Measurements held5
Confirmed unchanged1 time, most recently 10 October 2026
On Telegramt.me/blywuwa31

Topic

Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 2 October 2026 and assigned it the closest of 31 fixed categories, at 65% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.

Growth

364.57 August 2026 — 3 subscribers13 August 2026 — 3 subscribers9 September 2026 — 4 subscribers17 September 2026 — 6 subscribers10 October 2026 — 5 subscribers57 August 202610 October 2026
5 measurements spanning 64 days, net +2. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 3–6 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
10 Oct 2026, 14:015-1
17 Sept 2026, 08:556+2
9 Sept 2026, 14:184+1
13 Aug 2026, 16:023no change
7 Aug 2026, 19:063first reading

Engagement

11 posts held, back to 24 April 2026 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 page of Telegram’s post history, 20 posts per page.

Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 11 posts for this entry, the most recent from 27 April 2026. An engagement rate over an empty window would be a number about nothing.

Recent posts

27 Apr 2026, 15:55 UTC36 viewsread 13 August 2026

鉴于本频道人数较少,为了要有充足的时间准备让漂泊者们发现北落野并且提供宝贵的票数,本频道延迟到后天才结束本次投票并公布要出道的下一个库默明星。这四个吧的吧主或者是吧务做好准备哟~

27 Apr 2026, 06:50 UTC66 viewsread 13 August 2026
Poll

下一个该出道谁呢?由库洛玩家投票决定吧~

  1. 原神内鬼吧的吧务33%
  2. 反鸣潮吧的吧主或者吧务33%
  3. 新鸣潮内鬼吧的吧务17%
  4. 原神内鬼爆料吧的吧主或者吧务17%

Shares as published. No per-option vote count is published by Telegram, so none is shown.

25 Apr 2026, 06:26 UTC84 viewsread 13 August 2026
Photo

北落野出道新鸣潮内鬼吧吧主/原神内鬼吧吧务拟态: 玩家本人原神昵称:牟进康 原神UID:371726********6030 角色忌日:2004年8月20日 教育热线:*8053697349 贴吧ID:|拟态| 身份:米娇妻 玩家诞生地:提瓦特大陆山东省鄄城县彭楼镇西牟行政村西牟村167号 原神玩家生物爹:牟宗信 原神UID:372929********6030 角色忌日:1981年8月14日 教育热线:*3255403355 玩家诞生地:提瓦特大陆山东省鄄城县彭楼镇西牟行政村西牟村167号

24 Apr 2026, 10:01 UTC60 viewsread 13 August 2026

本频道将在明日正午出道新鸣潮内鬼吧吧主,原神内鬼吧吧务拟态

24 Apr 2026, 09:57 UTC256 viewsread 13 August 2026

经过北落野管理层四月会议决定,为了保卫库洛和正常的鸣潮玩家以及遏止社区一部分人滑坡行为,北落野频道在此成立和宣告。 北落野对于鸣潮社区一些歪屁股以及打着玩家权益大于一切为借口实际上对自家玩家进行攻击把鸣潮玩家喜欢的角色进行过分恶搞P图造谣制作恶梗的畸形麻辣仙人。 还有表面上站在鸣潮这边实际上是墙头草利用鸣潮玩家最后靠着鸣潮玩家恬不知耻社区胜利再进行歪屁股反鸣恶劣行为的。 最后还有无脑反对鸣潮这款游戏没有正常人思维跟风黑恶劣行为的米孝子。 对待以上这些库默北落野将为了保卫鸣潮和保护鸣潮社区的正常玩家将会使用特殊手段强制措施来制裁这群虫豸!

Showing the 11 most recent of 11 posts we hold for @blywuwa31. View and reaction counts are the latest single reading for each post, not a live figure, and a recent post is still accumulating both. A view count marked ≈ was rounded by Telegram before we ever saw it — t.me prints views in full below 1,000 and to three significant figures above, so ≈1,200,000 means somewhere between 1,150,000 and 1,249,999. Unmarked counts are exact. Text is reproduced from the public post preview and truncated for length.

Polls

The poll we hold for this entry, as Telegram rendered it when we read the post. A poll’s figures keep moving after that, so each one is dated.

27 Apr 2026, 06:50 UTCAnonymous Poll6 voters

下一个该出道谁呢?由库洛玩家投票决定吧~

  1. 原神内鬼吧的吧务33%
  2. 反鸣潮吧的吧主或者吧务33%
  3. 新鸣潮内鬼吧的吧务17%
  4. 原神内鬼爆料吧的吧主或者吧务17%

Shares as published. No per-option vote count is published by Telegram, so none is shown.

Percentages only — there are no per-option vote counts here, because Telegram publishes none. The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.

The shares need not add up to 100. Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.

Read from the 11 most recent posts we hold, published 24 April 2026 to 27 April 2026. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.

Cite this entry

A live page changes as we take new readings, so a citation should name the measurement it is based on, not just the URL. The line below cites the subscriber count as measured 10 October 2026 — this entry's latest reading, not the date you are reading this.

“北落野” (@blywuwa31), 5 subscribers as measured 10 October 2026. Telegram Register, tgregister.com/channel/blywuwa31.

Full measurement history, CC BY 4.0. Every reading this register holds for this entry, not just the latest one, as a dated, downloadable record: CSV · JSON. Free to use with attribution to tgregister.com. Each file carries its own generation timestamp, which is the figure to cite for exactly when the data was retrieved.