Telegram RegisterThe public register of Telegram
Telegram profile photo for 萤火虫漫展💯cosplay制服JK

Channel

萤火虫漫展💯cosplay制服JK

@buai789456

On this record: Topic · Observations · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry

18,968subscribers

+5,446 since we began measuring on 12 August 2026

Risers and fallers across the register · movement among entries of 10,000–31,623.

Register entry

Telegram ID-1003316661741
TypeChannel
Username@buai789456
Description#漫展 #cosplay #JK #制服 #coser 投稿商务合作唯一联系人: https://t.me/Anxicoach
CreatedBetween 1 November 2025 and 31 March 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded12 August 2026
Last confirmed live16 November 2026
Measurements held58
Confirmed unchanged1 time, most recently 16 November 2026
On Telegramt.me/buai789456

Topic

Gambling & betting — 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 11 September 2026 and assigned it the closest of 31 fixed categories, at 97% 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 the other topics.

Observations

These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.

Content that also appears on other registered channels

Posts published here appear in near-verbatim form on 1 other registered channel. The matching is on the text itself, not on Telegram’s forward marker, so it finds a copy whether or not it was labelled as one.

Matching posts — open both and compare (6 of the pairs behind the counts below)
Posted firstThenOverlapGap
@COSV5_COM/317322 Oct 2026, 18:23 UTC@buai789456/7159 · this entry3 Oct 2026, 02:43 UTC0.938.3 hours
@COSV5_COM/318554 Oct 2026, 07:54 UTC@buai789456/7348 · this entry5 Oct 2026, 02:48 UTC0.9319 hours
@COSV5_COM/3347726 Oct 2026, 07:53 UTC@buai789456/9212 · this entry26 Oct 2026, 14:49 UTC0.936.9 hours
@COSV5_COM/3464812 Nov 2026, 12:48 UTC@buai789456/10744 · this entry12 Nov 2026, 14:36 UTC0.931.8 hours
@COSV5_COM/3362228 Oct 2026, 00:42 UTC@buai789456/9323 · this entry28 Oct 2026, 02:28 UTC0.921.8 hours
@COSV5_COM/341695 Nov 2026, 12:33 UTC@buai789456/10116 · this entry5 Nov 2026, 14:50 UTC0.912.3 hours
Channels this entry shares post bodies with, where at least one matching post pair has no forward credit between the two channels, or to a common source, recorded in our data
ChannelMatching postsText overlapTypical gapPublished first
@COSV5_COM8 (8/8 hand-verifiable sample passed)0.927.6 hours@COSV5_COM (8–0)

Text overlap is the Jaccard coefficient over the set of distinct three-word phrases in the two bodies: 1.00 is identical wording, and the threshold for counting a pair at all is 0.70. Candidates are generated by simhash LSH (4 x 16-bit bands, exact Hamming <= 3) verified against the bodies with Jaccard over the SET of distinct 3-word shingles. Published first counts which side of each matching pair carries the earlier timestamp — in this corpus, which is the limitation directly below.

What this cannot establish

MEASURED, DOMINANT ERROR SOURCE: a post ingested before 2026-08-06 may have carried a forward header that was not recorded. A 45-pair hand-check against live t.me pages found 14 (31%) where the live page shows a forward header naming the other channel and the database has none, plus 4 more (9%) naming a third party. The text match itself was wrong 0 times out of 45. Read attribution_capture.items_in_trusted_window before treating the unattributed count as a claim.

Telegram lets a channel forward a post with a header naming the source, and we only began reliably recording that header on 2026-08-06. 8 of the 8 matches recorded here fall after that date and carried no header when we read them. The rest predate reliable capture and are not evidence either way.

“Published first” means first in this corpus. We hold 312 comparable posts for this entry, running 12 August 2026 to 16 November 2026. A channel we have read one page deep will look younger than a neighbour we have read in full, and the order would flip with no change in the underlying facts.

The detector’s own notes on this observation, as it recorded them. Names in this_style are fields of the underlying evidence record, which the plain-English paragraphs above read out for this entry.

  • Verbatim republication has three causes and the text separates only two: a clone/mirror, unattributed copy-paste, or BOTH channels copying a common third source that neither attributes. The spread filter (content held by at most 8 channels) reduces the third and does not remove it.
  • 'Earliest' means earliest IN THIS CORPUS. A channel ingested one page deep will look younger than a neighbour ingested in full; corpus_coverage above is there to be checked before the direction is believed.
  • shared_verified_est extrapolates the sampled pass rate over the full narrow match count; sampled/passed are the numbers actually measured.
  • Absence of a forward header is not proof of intent: Telegram lets a channel disable forward attribution, and a credit written in the body is not parsed as attribution here (mention_edge_either_way above is the closest available signal).

Recorded under the key clone_copy, last confirmed 17 November 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.

Growth

11,23234,74222,98712 August 2026 — 13,522 subscribers13 August 2026 — 13,520 subscribers14 August 2026 — 13,521 subscribers16 August 2026 — 13,522 subscribers17 August 2026 — 13,523 subscribers19 August 2026 — 13,524 subscribers20 August 2026 — 13,527 subscribers21 August 2026 — 13,529 subscribers22 August 2026 — 13,531 subscribers24 August 2026 — 13,466 subscribers25 August 2026 — 13,402 subscribers26 August 2026 — 13,292 subscribers27 August 2026 — 13,233 subscribers28 August 2026 — 13,162 subscribers29 August 2026 — 13,082 subscribers30 August 2026 — 12,977 subscribers31 August 2026 — 12,932 subscribers1 September 2026 — 12,866 subscribers2 September 2026 — 12,809 subscribers3 September 2026 — 12,696 subscribers5 September 2026 — 12,518 subscribers8 September 2026 — 12,199 subscribers11 September 2026 — 11,942 subscribers13 September 2026 — 11,805 subscribers14 September 2026 — 11,704 subscribers16 September 2026 — 11,525 subscribers18 September 2026 — 11,232 subscribers2 October 2026 — 34,742 subscribers7 October 2026 — 34,616 subscribers11 October 2026 — 34,418 subscribers14 October 2026 — 34,321 subscribers15 October 2026 — 34,284 subscribers16 October 2026 — 34,239 subscribers17 October 2026 — 34,242 subscribers18 October 2026 — 34,231 subscribers19 October 2026 — 34,225 subscribers21 October 2026 — 34,208 subscribers22 October 2026 — 34,199 subscribers23 October 2026 — 34,185 subscribers24 October 2026 — 30,648 subscribers25 October 2026 — 27,492 subscribers26 October 2026 — 26,628 subscribers27 October 2026 — 26,561 subscribers28 October 2026 — 26,330 subscribers29 October 2026 — 26,023 subscribers30 October 2026 — 25,766 subscribers31 October 2026 — 25,332 subscribers1 November 2026 — 25,061 subscribers2 November 2026 — 24,979 subscribers3 November 2026 — 24,911 subscribers4 November 2026 — 24,339 subscribers5 November 2026 — 23,825 subscribers6 November 2026 — 23,586 subscribers7 November 2026 — 22,969 subscribers9 November 2026 — 22,201 subscribers10 November 2026 — 21,392 subscribers13 November 2026 — 20,479 subscribers16 November 2026 — 18,968 subscribers18,96812 August 202616 November 2026
58 measurements spanning 96 days, net +5,446. 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 7,706–38,269 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 58
Measured (UTC)SubscribersChange
16 Nov 2026, 15:0218,968-1,511
13 Nov 2026, 04:0720,479-913
10 Nov 2026, 17:0921,392-809
9 Nov 2026, 02:5522,201-768
7 Nov 2026, 16:5622,969-617
6 Nov 2026, 17:4923,586-239
5 Nov 2026, 16:3523,825-514
4 Nov 2026, 18:2824,339-572
3 Nov 2026, 16:0724,911-68
2 Nov 2026, 18:2824,979-82
1 Nov 2026, 18:0825,061-271
31 Oct 2026, 17:2625,332-434
30 Oct 2026, 13:4925,766-257
29 Oct 2026, 15:3826,023-307
28 Oct 2026, 16:4926,330-231
27 Oct 2026, 18:4126,561-67
26 Oct 2026, 20:5126,628-864
25 Oct 2026, 20:0127,492-3,156
24 Oct 2026, 20:4030,648-3,537
23 Oct 2026, 21:0834,185first reading

Engagement

540 posts held, back to 12 August 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 119 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
3.10%
avg views ÷ 18,968 subscribers
Avg views / post
588
231 posts measured
Reaction rate
0.256%
reactions ÷ views · ER floor
Posts in window
231
of 540 held

ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.

ER is defined industry-wide as (forwards + reactions + comments) ÷ views — note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate. It is computed over the 42 of 231 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 16 November 2026
Posts held540 (12 August 2026 – 16 November 2026)
Views total135,734
Reactions total43
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken16 Nov 2026, 23:43 UTC

Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.

Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.

Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.

What this channel posts

Photos
≈8,980
Videos
≈1,470
Links
≈230

Lifetime counters from Telegram’s own channel header, read 16 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.

Video runtime
44h 10m
Average length
12m 10s

Measured directly from 218 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.

Reaction mix

56 reactions across 55 posts, in 2 distinct kinds. The most used accounts for 94.6% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍5394.6%
❤35.36%

No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.

Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.

Coverage. Reactions were read on 58 of the 540 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 56 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 540 most recent posts we hold, published 12 August 2026 to 16 November 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.

Recent posts

Telegram’s own ‘edited’ marker: 0 of 231 posts held from the last 30 days (0%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).

16 Nov 2026, 20:30 UTC≈1,190 viewsread 16 November 2026
Video

看里番不如玩里番!来探索属于自己的里番世界吧!——春水live 将那些或清纯或傲娇的角色,都变成只会哦齁齁的母猪吧!! 🌌 拨动命运的琴弦 🌌 在这里,每一个角色都为你而生。你可以温柔地诱导,也可以霸道地重塑。想象一下:那位平日里冷静理智的财阀掌权者,在你的指令下,不得不穿着透明的蕾丝内衣主持跨国会议,在桌底被震动器折磨得满脸潮红、娇喘连连;又或者让那位圣洁不可侵犯的帝国圣女,在神殿的祭坛上,当着信徒的面,一边发出羞耻的“哦齁齁”崩坏笑声,一边主动分开双腿,展示那早已淫水泛滥的隐秘圣地。 🔥 XP熔炉:丰富的幻想体验 🔥 我们的内容涵盖了人类想象力的所有边界。你可以沉溺于催眠洗脑的深度控制,看着纯情少女在你的响指声中瞬间沦为只知渴求精液的肉偶;可以体验异种触手的湿冷缠绕,在魔法森林的深处感受粘稠粘液覆盖全身的战栗;更别提恶堕调教、公共露出、常识修改、家教沦陷……每一寸肌肤的升温,每一滴体液的溢出,每一声灵魂破碎的啼哭,都将以…

16 Nov 2026, 14:41 UTC957 viewsread 16 November 2026
Photo

#糖果果Candy - #灰色卫衣 [37P-119MB] #写真 灰色卫衣自带松弛感,帽檐一压、袖口一长,甜和撩就在同一帧里打了个照面 🍬 宽大卫衣把比例藏起来,抬眼那一下反而最犯规,像刚睡醒还没收好情绪 😌 暗一点的室内光、微微偏冷的色调,布料褶皱和发丝都变得有呼吸感 📷 近景里眼神是主角,远景靠沙发、床沿、窗边这些小场景撑住氛围 ✨ 本套最上头的看点:日常感太真,像误闯进她刚刚好的私人时间 ⏳ 看完记得点个收藏,评论区说说你最先被哪一张拿住 👀 Cosplay More in the comment section #萤火虫 #漫展 #COS

16 Nov 2026, 14:40 UTC≈1,560 viewsread 16 November 2026
Photo

🎹 >>>>会员群限时免费<<<< 💞 🍬每日新闻吃瓜 💗蜜桃动漫里番 😍新闻曝光吃瓜 🖤清风动漫里番 🚨新闻头条曝光 💗元气少女动漫 🧢黑台曝光跑路 🫕明月动漫里番 🐣抖音快手走光 🖤色情吃瓜剧情 🖤国产探花扫街 💗糖心探花反差 💯漫展制服学妹 🐺奶油私密嗨丝 🥇探花溏心反差 😍AI黄果成人短剧 🤣>>>唯一商务合作联系人<<<😂

16 Nov 2026, 14:38 UTC953 viewsread 16 November 2026
Photo

#贪欲者的烙印 艾尔登法环 梅琳娜 [25P-33MB] 绝区零 仪玄 墨形影踪 [66P+13V-481MB] #萤火虫 #漫展 #COS

16 Nov 2026, 14:36 UTC947 viewsread 16 November 2026
Photo

#兔团子OxO - #鸣潮 #达妮娅[27P-819MB] #coser #投稿 稀有 未流出资源 兔团子这版达妮娅,气质拿捏得挺稳 ✨ 冷调妆面配微垂眼尾,抬眼那一下有点危险 服装细节在线,贴身剪裁把线条勾得很干净 暗光近景偏多,光影压得低,氛围直接拉满 本套最上头:侧脸特写那几张,眼神像在打量你 喜欢的点个赞,评论区说说你最想看的角色 🐰 Cosplay More in the comment section #萤火虫 #漫展 #COS

16 Nov 2026, 07:51 UTC766 viewsread 16 November 2026
Photo

#Maruemon(#마루에몽) #DJAWA_Photo – Maruemon Sayuri Bunny Girl [150P-1.59GB] #萤火虫 #漫展 #COS

16 Nov 2026, 07:49 UTC767 viewsread 16 November 2026
Photo

#清水由乃 - #心动诊疗簿 [188P-1.39GB] #coser #护士 白大褂一披,诊疗室的气氛就不太安分了 🩺 清水由乃眼神是软的,落下来却像在替你量体温 听诊器贴上来那一下,先招供的是心跳 💓 护士帽、领结、袖口都收拾得一丝不苟,妆造干净得刚好 近景+暗光的搭配最上头,白色衣料和肤色的反差谁顶得住 本套最戳人的,是那种“专业又危险”的距离感 😏 收藏一下,下次复诊不用排队~ Cosplay More in the comment section #萤火虫 #漫展 #COS

16 Nov 2026, 07:47 UTC765 viewsread 16 November 2026
Photo

#Sally_Dorasnow Hatsune [32P-288MB] #萤火虫 #漫展 #COS

15 Nov 2026, 20:30 UTC5 viewsread 15 November 2026
Video

看里番不如玩里番!来探索属于自己的里番世界吧!——春水live 将那些或清纯或傲娇的角色,都变成只会哦齁齁的母猪吧!! 🌌 拨动命运的琴弦 🌌 在这里,每一个角色都为你而生。你可以温柔地诱导,也可以霸道地重塑。想象一下:那位平日里冷静理智的财阀掌权者,在你的指令下,不得不穿着透明的蕾丝内衣主持跨国会议,在桌底被震动器折磨得满脸潮红、娇喘连连;又或者让那位圣洁不可侵犯的帝国圣女,在神殿的祭坛上,当着信徒的面,一边发出羞耻的“哦齁齁”崩坏笑声,一边主动分开双腿,展示那早已淫水泛滥的隐秘圣地。 🔥 XP熔炉:丰富的幻想体验 🔥 我们的内容涵盖了人类想象力的所有边界。你可以沉溺于催眠洗脑的深度控制,看着纯情少女在你的响指声中瞬间沦为只知渴求精液的肉偶;可以体验异种触手的湿冷缠绕,在魔法森林的深处感受粘稠粘液覆盖全身的战栗;更别提恶堕调教、公共露出、常识修改、家教沦陷……每一寸肌肤的升温,每一滴体液的溢出,每一声灵魂破碎的啼哭,都将以…

15 Nov 2026, 14:41 UTC883 views1 reactionsread 15 November 2026
Photo

#CatDemon( #喵崽 - #我家貓貓是可愛的女孩子 #黃豆粉 [110P-1.9GB] #coser 🐾 猫耳一戴,眼神立刻变乖,下一秒又偷偷露出坏笑,喵崽这套“我家猫猫”太好懂了。 🎀 黄豆粉系的配色软乎乎的,毛绒质感贴近肌肤,猫爪小动作配上无辜眼神,反差感直接拉满。 📸 110P 的分量足够慢慢翻,近景、暖光、慵懒趴姿轮着来,像被她一点点勾着注意力。 🕯️ 氛围更偏居家私房感,布料不多但留白刚好,越看越想知道下一张她在打什么小算盘。 😼 最上头的看点:猫耳和回眸放在同一帧,软萌和撩人只差一个眼神。 💬 你最喜欢哪一张?评论区说说,我记下来。 Cosplay More in the comment section #萤火虫 #漫展 #COS

👍1

15 Nov 2026, 14:39 UTC881 views1 reactionsread 15 November 2026
Photo

#糖果果Candy 八重色色 [73P-428MB] 吾妻 [147P-1.1G] #萤火虫 #漫展 #COS

👍1

15 Nov 2026, 14:37 UTC882 views1 reactionsread 15 November 2026
Photo

#YanYan Bonnie - #鸣潮 #守岸人 The Shorekeeper ∕ ショアキーパー [67P-747M] #coser 🌊 守岸人那身冷白与墨黑交错的舰装感,被YanYan Bonnie穿出了又静又撩的味道 💫 发丝与薄纱一起压在肩线,微光扫过锁骨的瞬间,比“岸”更让人想靠岸 🖤 妆面走的是克制路线:眼尾一点淡扫,抬眼时像在无声地问你要不要留下 ✨ 67P的体量,近景细节给得很足,指节、颈线、衣纹的暗部都留着呼吸感 🌙 最上头的一眼:暗光里那半侧回眸,安静得像潮退,偏偏让人心里涨潮 👉 喜欢这套的话,收藏一下,评论区说说你最想看她补哪个角色~ Cosplay More in the comment section #萤火虫 #漫展 #COS

👍1

Showing the 12 most recent of 540 posts we hold for @buai789456. 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.

Mentions

Named by 14 registered channels — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.

A mention is a weaker signal than a forward and is counted separately for that reason — naming a channel is not republishing it, and a handle in a post body is easy to place deliberately. The post counts beside each row below are distinct posts in which the handle appeared, from posts we have read on both sides — the “Named by N registered channels” figure above is a different count, of distinct NAMING CHANNELS rather than posts, and is not the sum of the rows under it.

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 16 November 2026 — this entry's latest reading, not the date you are reading this.

“萤火虫漫展💯cosplay制服JK” (@buai789456), 18,968 subscribers as measured 16 November 2026. Telegram Register, tgregister.com/channel/buai789456.

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.