Telegram RegisterThe public register of Telegram
Telegram profile photo for TIの日常

Channel

TIの日常

@TiezdneDF

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

11subscribers

+0 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1002717905107
TypeChannel
Username@TiezdneDF
Description也许是连续不断发生的奇迹吧 trash can https://t.me/+TBXPRzGZq3JlMjFl
CreatedBetween 1 June 2025 and 31 August 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded12 August 2026
Last confirmed live16 August 2026
Measurements held2
On Telegramt.me/TiezdneDF

Growth

117 August 2026 — 11 subscribers12 August 2026 — 11 subscribers7 August 202612 August 2026
2 measurements spanning 4 days. 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 10–12 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Aug 2026, 08:0011no change
7 Aug 2026, 23:5311first reading

Engagement

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

What this channel posts

Photos
3
Links
4

Lifetime counters from Telegram’s own channel header, read 12 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.

Reaction mix

13 reactions across 9 posts, in 7 distinct kinds. The most used accounts for 38.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
538.5%
🥰323.1%
🔥17.69%
🕊17.69%
😇17.69%
😢17.69%
🤔17.69%

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 9 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 13reactions 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 29 January 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.

Recent posts

25 Jun 2026, 12:13 UTC15 viewsread 12 August 2026

#摸鱼 最近沉迷一本修仙小说了,叫《我的模拟长生路》 设定还挺好玩的,正常修仙开挂都是一路往上走了,这本是主角能不停重开但练度也回到锚点,修仙也有诸多限制之类的 而且没有炼丹环节))))) 主要的看点就是在不同的轮回里看相同的人因为主角走上不同的路,顺便慢慢展开世界观 至少前期还蛮好看的 中间突然开始大水文+写一堆玄之又玄的东西,要不是书是22年开始写的我都怀疑全是ai古风了一遍 然后也很少描述重来一世是怎么布局规划的了,基本一句话概括了前期花了很多篇章描述的情节,换个说法就是直接开挂了 后面把目光投向救世的时候就慢慢走向烂尾,战力飙升,文字越来越水,金手指也用得少了; 看到1400章还水一堆字,结果出来看目录就1700章,很难想怎么收尾的 总之弃了,但只看前面500章左右的话挺不错的

14 Jun 2026, 13:49 UTC20 viewsread 12 August 2026
Forwarded from @SuzumeOfficialPhoto

[Twitter] 💬 Retweet 🔁 雀宮スズメ: >> View Tweet <<

10 Jun 2026, 15:20 UTC26 viewsread 12 August 2026

#无聊日常 最近基本在当ai监工,所以只能刷刷小手机 刷了不少网文改编的和各种重生归来的ai短剧,修桥/果园/做饭啥啥都有 3A生活) 单看短剧还行,ai视频没有网文的灌水环节,还有很酷的特效不用看文字想象了 但自己跑去看原文就一坨,公式化的套路,慢慢不依赖金手指了,就变成普通的水网文了 只有ai做的那部分因为经常用金手指,还会慢慢探索很有意思 想起来玩tr也是这样,联机的时候开荒期间是最热闹的,直到发展到一定程度开始BOSSrush后就只有几个一起打了,最后结档就3个人了 但搞建筑挺好玩的)

28 May 2026, 09:27 UTC25 views3 reactionsread 12 August 2026

下个月就要考试了还啥都没复习 要突击半个月了😠 这两天在用ai给社团的一个项目蹬一个前端,速度还挺快的,虽然有点一眼AI,加上跑出来后自己有种什么都没学到的空虚,总之有种说不清的感觉 社团的小登今天出现了不知道什么是ip和直接往git里上传key的问题,而且马上过几个月他们就要给新社员培训了,我们的社团会变成什么样(哽咽)

🥰3

26 May 2026, 07:50 UTC25 viewsread 12 August 2026

#黑暗料理日记 昨天去超市觅食的时候发现货架新上FIFA联动的乐事薯片,最后抱着试试看试毒的心理买了一包烤鱼薯条味和蒜香黄油味的 中午把吃剩的香干炒肉放饭上热了,结果不知道是油太多了还是饭睡太多了,总之黏糊糊的,勉强能吃) 剩了一些没吃完也没胃口了,干脆开了包烤鱼薯条味的吃了 味道很一般....硬要说就是薯片薯片味,能吃但啥都没有,吃着吃着反而吃出黄瓜味了 也没预期难吃到吐 不过进货了一批绿豆沙冰,好喝 说好的今天会下暴雨的结果一点都没下,不想动啊~~

10 May 2026, 06:05 UTC32 views1 reactionsread 12 August 2026

#黑暗料理日记 煮面吃结果生抽放太多了...吃一半实在反胃浪费掉了 然后找了点饼干和剩下一点的阿萨姆一起喝了,结果在肚子里发生了奇妙的化学反应 躺床不起ing

😇1

6 May 2026, 17:20 UTC32 viewsread 12 August 2026

#奇妙日常 前几天tg莫名收到了个bot的私信,大意是小群随机的招新,虽然自己是pm welcome但也太没头没尾了点.... 去顺着搜了下,还是想不出来怎么找到自己的,不过加群预览里倒是见到了熟悉的网友头像 最后也没加就是了,自己也社恐,加进去估计也是偶尔冷场的时候发点表情包吧 今天早上steam也莫名收到了个好友邀请,去对方主页里还看到专门提了句(我不会发送跳转外部网页的链接),好奇还是加了 刚刚突然私聊了句nihao,试探了下对方是用翻译的老外,接着就是问我知不知道buff和igxe(草 接下来要么是发个神秘小link盗号,要么是让我帮忙买点饰品之类的),最后自己说“抱歉没听过这俩平台”然后下线了 但我真的没玩过cs2诶 互联网还是太神奇了

5 Apr 2026, 07:17 UTC37 views1 reactionsread 12 August 2026

#黑暗料理日记 自从上次就没搞过咖喱了),都是煮小火锅自己吃 但老是看着在烧的水和火锅底料想"是不是太少了没味道"然后多丢一包,结果就是又辣又油 还是吃外卖健康)) 得学炒菜了

🤔1

24 Mar 2026, 02:58 UTC44 views1 reactionsread 12 August 2026

#黑暗料理日记 美团月付好多米了,果然延时消费会让人失去理智(? 总之今天中午整了点咖喱吃,好久没用刀切出来的土豆和胡萝卜都是形状各异的 放水也放太多了的样子,本来4块包的咖喱已经丢了2块进去了,煮到最后还是一滩水,最后干脆把剩下两坨也丢了进去 但还是没用,最后还是很介于咖喱汤和黏稠咖喱中间的感觉 因为土豆和胡萝卜切的有点太大了,说不上熟没熟,反正能吃 但和饭搭在一起完全变成咖喱汤泡饭了,不知道熟没熟的土豆和咖喱汤配合起来很怪,结果就是现在肚子里在打雷 反而是一开始丢进去煮的火锅肥牛卷还算能吃 剩下的等晚上再加工看看了,不行的话只能遗憾离场 厨房杀手下次注意)

1

Showing the 12 most recent of 20 posts we hold for @TiezdneDF. 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 12 August 2026 — this entry's latest reading, not the date you are reading this.

“TIの日常” (@TiezdneDF), 11 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/TiezdneDF.

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.