短期缺客户 长期缺直扫 永远缺必进
🤔11🤮8🤯7👎6🤬6😱6💩5😁5
Signed 跳跳

Channel
@k1314
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
12,972subscribers
-151 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1003379108679 |
|---|---|
| Type | Channel |
| Usernames | @buqiang @k1314 |
| Created | 4 December 2025 — measured — dated from the channel’s first post |
| First recorded | 8 August 2026 |
| Last confirmed live | 17 August 2026 |
| Measurements held | 9 |
| Confirmed unchanged | 1 time, most recently 17 August 2026 |
| On Telegram | t.me/k1314 |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 17 Aug 2026, 16:06 | 12,972 | -13 |
| 16 Aug 2026, 09:08 | 12,985 | -13 |
| 14 Aug 2026, 17:45 | 12,998 | +2 |
| 13 Aug 2026, 07:05 | 12,996 | -11 |
| 12 Aug 2026, 06:32 | 13,007 | -43 |
| 11 Aug 2026, 09:03 | 13,050 | -32 |
| 10 Aug 2026, 08:50 | 13,082 | -29 |
| 9 Aug 2026, 10:32 | 13,111 | -12 |
| 8 Aug 2026, 11:04 | 13,123 | first reading |
20 posts held, back to 4 December 2025 — the reader has reached the start of this channel’s public history, so this is the full archive Telegram still exposes. Read across 15 pagesof Telegram’s post history, 20 posts per page.
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.
| Window | Rolling 30 days · latest post in window 17 August 2026 |
|---|---|
| Posts held | 20 (4 December 2025 – 17 August 2026) |
| Views total | 198,900 |
| Reactions total | 666 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 17 Aug 2026, 19: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.
Lifetime counters from Telegram’s own channel header, read 17 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
Measured directly from 1 video 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.
1,272 reactions across 19 posts, in 25 distinct kinds. The most used accounts for 23.9% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 304 | 23.9% | |
| 👍 | 222 | 17.5% | |
| 🎉 | 217 | 17.1% | |
| 😁 | 175 | 13.8% | |
| 🔥 | 171 | 13.4% | |
| 🤡 | 25 | 1.97% | |
| 💩 | 23 | 1.81% | |
| 🤬 | 15 | 1.18% | |
| 👎 | 14 | 1.10% | |
| 🥰 | 14 | 1.10% | |
| 🤮 | 12 | 0.943% | |
| 🤔 | 11 | 0.865% | |
| ❤🔥 | 10 | 0.786% | |
| 👏 | 9 | 0.708% | |
| 🎃 | 8 | 0.629% | |
| 💯 | 7 | 0.55% | |
| 🤯 | 7 | 0.55% | |
| 😱 | 6 | 0.472% | |
| ⚡ | 5 | 0.393% | |
| 🎄 | 5 | 0.393% | |
| 5 further kinds | 12 | 0.943% |
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 19 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 1,272reactions 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 December 2025 to 17 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.
短期缺客户 长期缺直扫 永远缺必进
🤔11🤮8🤯7👎6🤬6😱6💩5😁5
Signed 跳跳
Video, posted without a caption
🎉19❤16👍11🔥10😁7
Signed 跳跳
别炒股,赌博好歹有运气可以赢,炒股除非有团队或内部消息,否则就让收割,时间没了精力没了,半辈子都在回本。
🔥13😁13🎉12👍12❤10💩1
Signed 龙叔(大盘猪杀手)
赢了享受生活,输了接受自己的平庸,无非是在努力工作个3年5年,起码比坐牢强吧。世界上没有过不去的坎,以前被深套过一次,都做好要花十年回本的准备了,事实上三年后就回本了。就当自己又念了一次大学,几年很快的,一眨眼就过去了。
🎉13❤12🔥12😁9👍7👎1💩1
Signed 龙叔(大盘猪杀手)
朋友圈说一句 合作我永远可以和大家磨合 如果欺骗我 不留情面
🎉32👍25❤18🔥14😁14👎2
Signed 龙叔(大盘猪杀手)
钱一天天少,你焦虑到不行。生命一天天少,你却一点不在乎。 因为你穷过,但是没死过。 你只在乎你还剩多少钱,却不在乎你还剩下多少年。
🎉78👍66😁61❤60🔥59👎1
Signed 龙叔(大盘猪杀手)
停在港口的船很安全, 但亲爱的,那不是造船的意义。
🎉19🔥15😁14❤13👍9💯3
Signed 龙叔(大盘猪杀手)
三千八百约了一整晚,推开民宿房门她熟门熟路扯掉外套,指尖松着吊带就要往床边坐,我伸手拦住她,把落在沙发上的卫衣递过去,让她先把衣服穿好,打算带她出门吃碗热馄饨。走在深秋的街道,晚风卷着枯叶擦过我们脚边,她一路频频侧头打量我,眼底全是藏不住的困惑,街边路灯昏黄的光落在她单薄的脸上,她摸出兜里廉价的薄荷烟点上,火光一亮又迅速暗下去,像她压在心底无处诉说的委屈。馄饨铺白雾腾腾,我拿起勺子给她舀了满满一碗肉馅馄饨,轻声和她说吃完去河边散散步,她指尖攥紧一次性筷子,心里满是不解,却碍于这层交易关系,只能轻轻点了点头。河堤夜风寒凉,她冻得缩起肩膀,我脱下身上厚外套裹在她肩头,她猛地一僵,慌忙后退半步,慌张问我是不是现在就要回去,我望着河面晃动的波光笑了笑,告诉她只是怕她着凉,没有别的意思。那一晚她安静了许多,不再刻意摆出逢场作戏的讨好模样,安安静静跟在我身后,路过街角一家手作银饰小店时,她脚步骤然停下,目光死死黏在橱窗里刻字小银牌上,我牵起…
❤21🎉15👍14🔥12😁7👎2🎃1
Signed 龙叔(大盘猪杀手)
今年,我祝愿你能少些—— 少些信息 📣 少些饭局 🍷 少些娱乐 😙 少些交流 📞 少些外债 💱 这些东西你已经拥有得太多了,它们阻碍了你的平静 🧊、健康 💪、睡眠 💤 和创造力 🖼。 新年快乐!🎆
❤27👍5
Signed 龙叔(大盘猪杀手)
File, posted without a caption
❤4
Signed 跳跳
赏千两金 封万户侯
😁39🎉29🔥28❤24👍19💘3💩3🙏2
Signed 龙叔(大盘猪杀手)
大盘猪集团: @tuilu 常规空降色刷: @longnu
❤23🔥6👍4🥰3👏2😁1
Signed 龙叔(大盘猪杀手)
Showing the 12 most recent of 20 posts we hold for @k1314. 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 — 1,471,758 of 1,481,306entries 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.
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.
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.
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 17 August 2026 — this entry's latest reading, not the date you are reading this.
“兰亭序” (@k1314), 12,972 subscribers as measured 17 August 2026. Telegram Register, tgregister.com/channel/k1314.
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.