Telegram RegisterThe public register of Telegram
Telegram profile photo for π‘€π“‡π“Žπ“‚ °🌊

Channel

π‘€π“‡π“Žπ“‚ °🌊

@DaillyLife

Has discussion group

On this record: Topic Β· Growth Β· Engagement Β· Citations Β· Telegram's recommendations Β· Cite this entry

2,137subscribers

-60 since we began measuring on 6 August 2026

Risers and fallers across the register Β· movement among entries of 1,000–3,162.

Register entry

Telegram ID-1001237992299
TypeChannel
Username@DaillyLife
CreatedBetween 1 March 2018 and 31 July 2021 β€” estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded19 September 2026
Last confirmed live25 September 2026
Measurements held16
Confirmed unchanged1 time, most recently 25 September 2026
On Telegramt.me/DaillyLife

Topic

Other / unclassifiable β€” a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 19 September 2026 and assigned it the closest of 31 fixed categories, at 83% 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 why it has no browse page of its own yet.

Growth

2,1372,1982,167.56 August 2026 β€” 2,197 subscribers7 August 2026 β€” 2,198 subscribers10 August 2026 β€” 2,194 subscribers12 August 2026 β€” 2,190 subscribers16 August 2026 β€” 2,182 subscribers19 August 2026 β€” 2,180 subscribers22 August 2026 β€” 2,177 subscribers25 August 2026 β€” 2,175 subscribers28 August 2026 β€” 2,173 subscribers31 August 2026 β€” 2,166 subscribers3 September 2026 β€” 2,164 subscribers8 September 2026 β€” 2,156 subscribers13 September 2026 β€” 2,155 subscribers17 September 2026 β€” 2,146 subscribers19 September 2026 β€” 2,146 subscribers25 September 2026 β€” 2,137 subscribers6 August 202625 September 2026
16 measurements spanning 50 days, net -60. 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 2,128–2,207 and does not start at zero.
Measurement log β€” every subscribers count we have recorded
Measured (UTC)SubscribersChange
25 Sept 2026, 14:012,137-9
19 Sept 2026, 02:102,146no change
17 Sept 2026, 01:002,146-9
13 Sept 2026, 01:572,155-1
8 Sept 2026, 17:352,156-8
3 Sept 2026, 04:182,164-2
31 Aug 2026, 10:032,166-7
28 Aug 2026, 14:162,173-2
25 Aug 2026, 12:222,175-2
22 Aug 2026, 20:492,177-3
19 Aug 2026, 08:072,180-2
16 Aug 2026, 17:462,182-8
12 Aug 2026, 21:582,190-4
10 Aug 2026, 07:402,194-4
7 Aug 2026, 11:302,198+1
6 Aug 2026, 22:012,197first reading

Engagement

Posts not read yet. This entry is on the register from its profile alone; the post reader has not reached it. Engagement figures appear here once posts have actually been measured β€” we do not publish a rate before we have the readings behind it.

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

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

Named by 2 registered channels β€” 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.

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.

Appears in Telegram’s recommendations for other channels

The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly β€” each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.

سیاوش ادبیاΨͺ
@siavash_adabiat Β· 21,116
Telegram ranks this channel #52 of 68 here β€” alongside 67 others β€” read 23 September 2026

This channel appears in 1 seed channel's Telegram-generated recommendation list in total. Each is Telegram’s list for THAT channel, not this one β€” see how this is measured.

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 25 September 2026 β€” this entry's latest reading, not the date you are reading this.

β€œπ‘€π“‡π“Žπ“‚ Β°πŸŒŠβ€ (@DaillyLife), 2,137 subscribers as measured 25 September 2026. Telegram Register, tgregister.com/channel/DaillyLife.

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.