🌸欢迎加入预览群 ✨每日更新优质资源 本群为预览群:预览群以内容片段为主,完整内容请加入会员群观看点这里加入会员群
❤1

Channel
@jintnllm
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
44,483subscribers
+1,077 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 31,623–100,000.
| Telegram ID | -1003433518601 |
|---|---|
| Type | Channel |
| Username | @jintnllm |
| Created | Between 1 November 2025 and 31 March 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 30 August 2026 |
| Measurements held | 21 |
| Confirmed unchanged | 1 time, most recently 30 August 2026 |
| On Telegram | t.me/jintnllm |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 30 Aug 2026, 18:37 | 44,483 | +22 |
| 29 Aug 2026, 16:53 | 44,461 | +30 |
| 28 Aug 2026, 18:37 | 44,431 | -4 |
| 27 Aug 2026, 22:04 | 44,435 | +40 |
| 26 Aug 2026, 21:23 | 44,395 | +31 |
| 25 Aug 2026, 18:03 | 44,364 | +23 |
| 24 Aug 2026, 17:24 | 44,341 | +67 |
| 23 Aug 2026, 00:05 | 44,274 | +61 |
| 21 Aug 2026, 12:08 | 44,213 | +55 |
| 20 Aug 2026, 12:36 | 44,158 | +51 |
| 19 Aug 2026, 16:06 | 44,107 | +33 |
| 18 Aug 2026, 13:35 | 44,074 | +86 |
| 17 Aug 2026, 10:18 | 43,988 | +70 |
| 15 Aug 2026, 20:23 | 43,918 | +109 |
| 14 Aug 2026, 09:18 | 43,809 | +35 |
| 12 Aug 2026, 21:58 | 43,774 | +68 |
| 11 Aug 2026, 22:26 | 43,706 | +91 |
| 10 Aug 2026, 19:24 | 43,615 | +91 |
| 9 Aug 2026, 17:42 | 43,524 | +59 |
| 8 Aug 2026, 17:40 | 43,465 | first reading |
118 posts held, back to 3 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 66 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. It is computed over the 78 of 118 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 30 August 2026 |
|---|---|
| Posts held | 118 (3 August 2026 – 30 August 2026) |
| Views total | 418,654 |
| Reactions total | 126 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 31 Aug 2026, 01:49 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 31 August 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.
126 reactions across 55 posts, in 5 distinct kinds. The most used accounts for 93.7% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 118 | 93.7% | |
| 🔥 | 3 | 2.38% | |
| 👍 | 2 | 1.59% | |
| 👏 | 2 | 1.59% | |
| 🤯 | 1 | 0.794% |
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 78 of the 118 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 126reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 118 most recent posts we hold, published 3 August 2026 to 30 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.
🌸欢迎加入预览群 ✨每日更新优质资源 本群为预览群:预览群以内容片段为主,完整内容请加入会员群观看点这里加入会员群
❤1
#菠萝啤beer 极品身材颜值都比较在线的丰满肥臀御姐反差感拉满
#好战份子 #xgga91 推特原创博主极品身材黑丝肥臀打桩视角代入感很强
#feelo3o #羊 推特极品身材蜂腰巨乳黑丝翘臀
#伊藤诚 #派大星 推特原创博主打桩极品丰乳完美腰臀比每一帧画面都是极品
#一条肌肉狗 #MuscledogH 推特原创猛男博主打桩调教极品高挑身材长腿黑丝肥臀
#跳跳羊 #tiaotiaosheep 极品颜值长腿油亮黑丝高跟翘臀身材御姐
#姚漫川 极品身材曼妙曲线细腰肥臀长腿黑丝高跟御姐
#饭饭吖 推特原创绿帽博主长腿黑丝长腿圆润翘臀
#七月七 #wz12241 推特原创博主打桩极品长腿黑丝肥臀御姐
#江南第一深情 #元歌的恋爱日记 推特原创博主这位不用多介绍了女主都很极品身材很不错
#噗噗 #pupu 推特极品颜值肉感肥臀御姐身材微胖中的极品
Showing the 12 most recent of 118 posts we hold for @jintnllm. 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.
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 30 August 2026 — this entry's latest reading, not the date you are reading this.
“日理万姬” (@jintnllm), 44,483 subscribers as measured 30 August 2026. Telegram Register, tgregister.com/channel/jintnllm.
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.