🤍New post | tags: #art credit : caroosoft on 💬 post | @dailyalbedocf bot :: @nonbailyalbedobot
custom 521794936411418627313💋7❤6💘2
Signed nightmare:
![Telegram profile photo for [non] Daily Albedo + cf](https://cdn.tgregister.com/av/22/22c3fbb97ef6c862ed18040bcb263165023ff396826de1f107a45cab147e23d7.jpg)
Channel
@dailyalbedocf
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
205subscribers
-13 since we began measuring on 13 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002311481782 |
|---|---|
| Type | Channel |
| Username | @dailyalbedocf |
| Created | Between 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 13 August 2026 |
| Last confirmed live | 12 September 2026 |
| Measurements held | 6 |
| Confirmed unchanged | 1 time, most recently 12 September 2026 |
| On Telegram | t.me/dailyalbedocf |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Sept 2026, 22:37 | 205 | -3 |
| 5 Sept 2026, 20:15 | 208 | -1 |
| 28 Aug 2026, 21:57 | 209 | -1 |
| 22 Aug 2026, 15:33 | 210 | -8 |
| 14 Aug 2026, 10:35 | 218 | no change |
| 13 Aug 2026, 12:33 | 218 | first reading |
18 posts held, back to 13 September 2025 — 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 page of 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 18 posts for this entry, the most recent from 25 September 2025. An engagement rate over an empty window would be a number about nothing.
245 reactions across 18 posts, in 4 distinct kinds. The most used accounts for 43.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5217949364114186273 | 106 | 43.3% | |
| ❤ | 56 | 22.9% | |
| 💘 | 47 | 19.2% | |
| 💋 | 36 | 14.7% |
Custom emoji. One row above is a Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The count beside it is Telegram’s.
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 18 of the 18 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 245 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 18 most recent posts we hold, published 13 September 2025 to 25 September 2025, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
🤍New post | tags: #art credit : caroosoft on 💬 post | @dailyalbedocf bot :: @nonbailyalbedobot
custom 521794936411418627313💋7❤6💘2
Signed nightmare:
🤍New post | tags: #art #other #official credit : mintificial on 💬 🤩 :: Арт на HoYoFair post | @dailyalbedocf bot :: @nonbailyalbedobot
custom 521794936411418627311❤8💋2💘1
Signed nightmare:
🤍New post | tags: #art #other credit : 0sei6 on 💬 post | @dailyalbedocf bot :: @nonbailyalbedobot
custom 52179493641141862738💘5
Signed nightmare:
🤍New post | tags: #art credit : dulioon_ on 💬 post | @dailyalbedocf bot :: @nonbailyalbedobot
custom 52179493641141862739❤7💋4💘3
Signed nightmare:
🤍New post | tags: #art credit : rinbedo on 💬 post | @dailyalbedocf bot :: @nonbailyalbedobot
💘6💋5
Signed nightmare:
🤍New post | tags: #art credit : _tomei_trans on 💬 post | @dailyalbedocf bot :: @nonbailyalbedobot
❤6custom 52179493641141862734💘2
Signed nightmare:
🤍New post | tags: #art credit : kinrama_dekin on 💬 post | @dailyalbedocf bot :: @nonbailyalbedobot
❤7custom 52179493641141862737💘2
Signed nightmare:
🤍New post | tags: #art #other credit : 66_norakura on 💬 post | @dailyalbedocf bot :: @nonbailyalbedobot
custom 521794936411418627311💘4
Signed nightmare:
🤍New post | tags: #art credit : n0kio on 💬 post | @dailyalbedocf bot :: @nonbailyalbedobot
custom 521794936411418627311❤3💘2
Signed nightmare:
🤍New post | tags: #art #other credit : unagiiri on 💬 🤩 :: На этом мы заканчиваем празднование дня рождения! post | @dailyalbedocf bot :: @nonbailyalbedobot
💋7💘6❤5custom 52179493641141862735
Signed nightmare:
🤍New post | tags: #art credit : mea_lost on 💬 post | @dailyalbedocf bot :: @nonbailyalbedobot
💘3custom 52179493641141862733❤2
Signed nightmare:
🤍New post | tags: #art credit : Aji_11300913 on 💬 post | @dailyalbedocf bot :: @nonbailyalbedobot
custom 52179493641141862734💋2❤1💘1
Signed nightmare:
Showing the 12 most recent of 18 posts we hold for @dailyalbedocf. 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.
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.
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.
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 12 September 2026 — this entry's latest reading, not the date you are reading this.
“[non] Daily Albedo + cf” (@dailyalbedocf), 205 subscribers as measured 12 September 2026. Telegram Register, tgregister.com/channel/dailyalbedocf.
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.