Shit game but full of wonderful people 😑
❤17

Channel
@DavidiaDiary
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
243subscribers
+0 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001177058762 |
|---|---|
| Type | Channel |
| Username | @DavidiaDiary |
| Description | 新世纪独立自主的深圳女启蒙军 @Davidia42 的咸鱼日记 尽量每天说一些Ingress 有关的废话 (咕咕🐦) |
| Created | Between 1 April 2018 and 31 July 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 15 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/DavidiaDiary |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 7 Aug 2026, 02:32 | 243 | no change |
| 6 Aug 2026, 09:26 | 243 | first reading |
14 posts held, back to 17 April 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 pageof 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 14 posts for this entry, the most recent from 25 June 2026. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 7 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.
242 reactions across 13 posts, in 10 distinct kinds. The most used accounts for 34.7% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 84 | 34.7% | |
| 👏 | 59 | 24.4% | |
| 👍 | 32 | 13.2% | |
| 🎉 | 21 | 8.68% | |
| 😱 | 12 | 4.96% | |
| 🤣 | 12 | 4.96% | |
| 🫡 | 10 | 4.13% | |
| 🔥 | 8 | 3.31% | |
| 🤔 | 2 | 0.826% | |
| 🥰 | 2 | 0.826% |
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 13 of the 14 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 242reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 14 most recent posts we hold, published 17 April 2026 to 25 June 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.
Shit game but full of wonderful people 😑
❤17
集卡爱好者很开心! 参与了的各位组织者辛苦了🌷 🐜:你到底买了多少 我:大人的事小孩子不要多嘴
😱12❤4🥰2
激动的心 瘫痪的腿 炎热的日头 强硬的嘴 上次MD制霸还是上次了⭐
👏24🎉14
早知道差一个就开牌昨晚就不睡觉了(
啊?
👏21🫡10❤4
该死的佛山md凭什么卡做得这么好看❌❌❌❌❌❌
❤4
Orion Series 收工啦🐈 P神的任务在此处起到了一个分割线的作用哈哈哈
❤7🎉7🤔2
Following the Enlightened victory in the Kure City Orion Anomaly, the XM in the scanners has turned green! It is currently unknown if this is just a coincidence and how long will the XM remain this colour. We'll monitor the scanner in the next hours and keep you updated if we detect any changes. @IUENG
🔥4
吴惊吴险,又到吴点! 大家辛苦啦,收工~🥳 Welcome to the Ingress Fifth Saturday
❤18👏11
これは呉です!
❤5👍5
你们知道我想说什么(((((( 🔗 广州启蒙军公众号文章阅读链接 👛 佛山MD周边预购链接 友情提示:预购截止时间为明日(5月26日)晚上24:00,目前没有二开的预期,预购者从速
❤5🔥3👍2
澳利澳 XMA 还是很开心的☺️
❤18👍9
Showing the 12 most recent of 14 posts we hold for @DavidiaDiary. 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.
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.
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 7 August 2026 — this entry's latest reading, not the date you are reading this.
“散打的嘤格瑞斯日志” (@DavidiaDiary), 243 subscribers as measured 7 August 2026. Telegram Register, tgregister.com/channel/DavidiaDiary.
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.