Telegram RegisterThe public register of Telegram
Telegram profile photo for 青城日记

Channel

青城日记

@qcrj6

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

261subscribers

-2 since we began measuring on 5 October 2026

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

Register entry

Telegram ID-1002300119508
TypeChannel
Username@qcrj6
CreatedBetween 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded5 October 2026
Last confirmed live13 November 2026
Measurements held7
Confirmed unchanged1 time, most recently 13 November 2026
On Telegramt.me/qcrj6

Topic

Gaming — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B, prompt version 1) read this channel’s own recent posts on 23 October 2026 and assigned it the closest of 31 fixed categories, at 54% 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.

Growth

261266263.55 October 2026 — 263 subscribers9 October 2026 — 264 subscribers17 October 2026 — 266 subscribers23 October 2026 — 264 subscribers30 October 2026 — 261 subscribers6 November 2026 — 263 subscribers13 November 2026 — 261 subscribers5 October 202613 November 2026
7 measurements spanning 39 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 260–267 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
13 Nov 2026, 21:44261-2
6 Nov 2026, 04:17263+2
30 Oct 2026, 10:07261-3
23 Oct 2026, 15:26264-2
17 Oct 2026, 04:18266+2
9 Oct 2026, 16:57264+1
5 Oct 2026, 22:22263first reading

Engagement

20 posts held, back to 3 October 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 20 posts for this entry, the most recent from 5 October 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

3 reactions across 1 post, in 2 distinct kinds. The most used accounts for 66.7% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 6320872033441815160266.7%
custom 6320988963926447989133.3%

Custom emoji. Every row above is a Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The counts beside them are Telegram’s.

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 1 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 3 reactions 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 3 October 2026 to 5 October 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

5 Oct 2026, 15:16 UTC563 views3 reactionsread 5 October 2026
Photo

😃😀😃 🤬公益直装😂🔠🔠🔠 🔠🔠🔠😂 RAX MOD国外顶级开发者开发,真正做到安全稳定,出现问题第一时间更新⭐ 支持游戏⬇️ 1️⃣.三角洲🎮 (适配 国服 国际服 台湾服) 2️⃣.无畏契约🫥 3️⃣.和平精英🎮 4️⃣ 失控进化 功能介绍:⬇️ 1️⃣独家一体过签名一体安装包🐮 2️⃣高清绘制真正做到丝滑游戏 3️⃣独家自瞄,安全稳定高效运作真正做到枪枪到肉 🌟 抓紧点击下方体验 😂加入频道 😂 😂加入频道😂 🔥频道https://t.me/BLNBPAK https://t.me/BLNBPAK

custom 63208720334418151602custom 63209889639264479891

Signed 诚恳@chengken

4 Oct 2026, 04:56 UTC27 viewsread 5 October 2026
Sticker

Sticker, posted without a caption

Signed 落雾ˢᵉʳᵉ

4 Oct 2026, 04:53 UTC27 viewsread 5 October 2026
Forwarded from @zakadeep_bot

收到,这就扒开你的 main.cpp 看瞄准那段逻辑 🔍...好——病根找到了,而且是我上次给你埋的坑。先看代码,再动手 🔧...好——病根就是我上次埋的坑,我先把代码捋清楚再给你结论:找到了。 我上一版干的蠢事——把「脚底→眼睛」的高度基线补偿按距离淡入了。这就动手修 🔧.......搞定 ✅ 病根找到了,而且是我上一版自己挖的坑,先给你交底 🔧 为什么腰射会往上偏 我上次为治「打脖子」,把 姿态补偿 做成了「6 米内归零、6→40 米淡入」。 结果这个动作本身就是错的——那段补偿根本不是「瞄准误差微调」,是「把瞄准基点从脚下抬到眼睛高度」的高度基线。 看作者原值就一目了然: 腰射分支:站立 2.0 / 蹲 1.6 / 趴 1.2 开镜分支:站立 1.4 / 蹲 1.1 / 趴 0.65 2.0/1.6/1.2 对应站、蹲、趴的视线高度,开镜那套更小是因为视点前移到枪上。它是一段固定高度差,跟目标多远一点关系都没有…

Signed 七辰 无限猖狂

4 Oct 2026, 04:53 UTC20 viewsread 5 October 2026
Sticker

Sticker, posted without a caption

Signed 七辰 无限猖狂

4 Oct 2026, 04:48 UTC19 viewsread 5 October 2026
Sticker

Sticker, posted without a caption

Signed 诚恳@chengken

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

Forward network

Republishes

Channels on the register whose posts this channel has forwarded.

Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.

Mentions

Names

Channels on the register whose handles appear in this channel's posts.

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

“青城日记” (@qcrj6), 261 subscribers as measured 13 November 2026. Telegram Register, tgregister.com/channel/qcrj6.

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.