Telegram RegisterThe public register of Telegram

Channel

其乐融融(秘密基地)

@qileror

On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry

2,408subscribers

+127 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1003725551760
TypeChannel
Username@qileror
CreatedBetween 1 February 2026 and 30 June 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live10 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 10 August 2026
On Telegramt.me/qileror

Growth

2,2812,4082,344.57 August 2026 — 2,281 subscribers7 August 2026 — 2,292 subscribers10 August 2026 — 2,408 subscribers7 August 202610 August 2026
3 measurements spanning 3 days, net +127. 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 2,262–2,427 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
10 Aug 2026, 13:122,408+116
7 Aug 2026, 18:482,292+11
7 Aug 2026, 10:162,281first reading

Engagement

20 posts held, back to 4 August 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 2 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
21.4%
avg views ÷ 2,408 subscribers
Avg views / post
516
20 posts measured
Reaction rate
0.533%
reactions ÷ views · ER floor
Posts in window
20
of 20 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.

What these figures were computed from
WindowRolling 30 days · latest post in window 6 August 2026
Posts held20 (4 August 20266 August 2026)
Views total10,311
Reactions total55
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken7 Aug 2026, 16: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.

Reaction mix

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

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
5396.4%
👍23.64%

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 20 of the 20 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 55reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 20 most recent posts we hold, published 4 August 2026 to 6 August 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

6 Aug 2026, 14:32 UTC547 views2 reactionsread 7 August 2026
Photo

#绿茶 #嫩妹 终于让我约到嫩妹了,这次的妹子皮肤白皙,关键是淫水还特别多,中途也是品尝了一下,别说,嫩妹操起来有种别样的感觉,最后也是射到妹子头上,妹子有点嫌弃但是无伤大雅哈哈 👅👅👉🏻点击我查看视频👈🏻👅👅

2

6 Aug 2026, 14:32 UTC580 views2 reactionsread 7 August 2026
Photo

#我的枪好长 #极品 桃子这次穿了一个蟒蛇情趣,前面跪着给兄弟口,我在旁边录制的时候看得都硬了,兄弟也是健身的嘎嘎猛,给桃子操的嗷嗷叫哈哈 👅👅👉🏻点击我查看视频👈🏻👅👅

2

6 Aug 2026, 14:26 UTC342 views3 reactionsread 7 August 2026
Photo

#萌宅卡 #极品 可爱妹子应聘了一个成人玩具试用师,想着工资高应该不会有问题吧,没想到用完道具后,变得好敏感,直接被欲望控制了 👅👅👉🏻点击我查看视频👈🏻👅👅

3

6 Aug 2026, 14:26 UTC427 views3 reactionsread 7 August 2026
Photo

#龙傲天 #嫩妹 这次花大价钱约了一个大圈妹子,长得那叫一个可爱,这么清纯的妹子操起来那叫一个快活,后面也是拔套让她给我口出来了,太值了 👅👅👉🏻点击我查看视频👈🏻👅👅

3

6 Aug 2026, 14:26 UTC469 views3 reactionsread 7 August 2026
Photo

#萌崽儿 #极品 有性瘾的少女遇上了多金的继父,为了让他爆金币也为了多要点生活费,直接献出自己的身体了 👅👅👉🏻点击我查看视频👈🏻👅👅

3

6 Aug 2026, 14:26 UTC517 views3 reactionsread 7 August 2026
Photo

#工藤静香 #ntr 新婚夜嫂子爬上了我的床,跟我缠绵,我一时没忍住犯了错误,没办法只能一错再错,做了好几次 👅👅👉🏻点击我查看视频👈🏻👅👅

3

6 Aug 2026, 14:14 UTC287 views3 reactionsread 7 August 2026
Photo

#嫩小兔 #ntr 独守空房的人妻很寂寞呢,有一段时间没有和老公愛愛,内心很空虚呢,趁次机会趁虚而入,直接给这寂寞人妻解解渴。 👅👅👉🏻点击我查看视频👈🏻👅👅

3

6 Aug 2026, 14:14 UTC318 views3 reactionsread 7 August 2026
Photo

#七喜小姐 #极品 长得挺清纯的小菇凉没想到内心特别想要被粗鲁对待呢,清纯的外表心里装了一个m的心,也是被狠狠调教了好吧 👅👅👉🏻点击我查看视频👈🏻👅👅

3

6 Aug 2026, 14:06 UTC253 views3 reactionsread 7 August 2026
Photo

#龙之介 #制服 长得帅身材好就是吃香啊,这个帅哥博主又约上反差御姐了,还穿着情趣衣和丝袜,看着撸点满满啊。 👅👅👉🏻点击我查看视频👈🏻👅👅

3

6 Aug 2026, 14:06 UTC250 views3 reactionsread 7 August 2026
Photo

#凉仔 #制服 富少留学遇到了可爱毛妹,这个妹子浑身上衣白白嫩嫩的,喘的声音也很中性化,不会像其他毛妹那样,喘的很好听,直接狠狠展示中国龙 👅👅👉🏻点击我查看视频👈🏻👅👅

3

6 Aug 2026, 14:06 UTC283 views4 reactionsread 7 August 2026
Photo

#意淫自己妹妹 #极品 这次和妹妹一起回老家,在外公家楼顶上直接野战,很刺激,妹妹敏感度直接提升一个等级夹的好紧,中途还让阿伯看到了哈哈应该没事 👅👅👉🏻点击我查看视频👈🏻👅👅

4

6 Aug 2026, 14:06 UTC268 views3 reactionsread 7 August 2026
Photo

#素人 #极品 这个妹子长得太符合我的审美了,清纯的脸蛋,还很反差,做爱的时候反馈太棒了,很喜欢哈哈 👅👅👉🏻点击我查看视频👈🏻👅👅

3

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

Citation-graph rank

Citation-graph rank — 944,106 of 1,151,006entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

Mentions

Named by 1 registered channel — 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.

Named by

Channels on the register whose posts name this channel's handle.

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

“其乐融融(秘密基地)” (@qileror), 2,408 subscribers as measured 10 August 2026. Telegram Register, tgregister.com/channel/qileror.

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.