Channel
@Daniel_dfnet
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
8subscribers
+0 since we began measuring on 11 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1004402786137 |
|---|---|
| Type | Channel |
| Username | @Daniel_dfnet |
| Created | Between 1 June 2026 and 8 August 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 12 August 2026 |
| Last confirmed live | 12 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/Daniel_dfnet |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Aug 2026, 14:02 | 8 | no change |
| 11 Aug 2026, 01:45 | 8 | first reading |
20 posts held, back to 8 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 1 pageof 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.
| Window | Rolling 30 days · latest post in window 12 August 2026 |
|---|---|
| Posts held | 20 (8 August 2026 – 12 August 2026) |
| Views total | 221 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 12 Aug 2026, 14:02 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 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.
[ 🌼 запись ОО2. ] " думаю, мне следует исследовать новые окрестности на этой неделе. недавно я чуть не заблудился в этом гребаном лесу, но, как оказалось, просто свернул не туда. не стоит задумываться о чем-то когда идешь в такой глуши.. благо я встретил одну свою знакомую, которая помогла мне найти дорогу на юго-запад. " " ..не знаю, потерялся бы я совсем, если бы не она. а если бы и потерялся… чтож, не буду …
Sticker, posted without a caption
Sticker, posted without a caption
[ 🌻 connect.. ] 𓏏𓏏 Даниэль глянул в сторону куполов, а затем снова на Ксистер. не идти на встречу, так не идти, вроде бы все понятно.. он кивнул, напоследок попрощавшись. — понял. благодарю вас, всего хорошего. 𓏏𓏏 тот пошел в нужное ему направление, снова перебираясь сквозь небольшие кусты, оглядываясь по сторонам и сжимая рукоять ножа в кармане своего худи по крепче. неизвестная тропинка с деревьями и другими …
сапп : я тебя проклял 😘
Sticker, posted without a caption
Sticker, posted without a caption
[ 🌻 connect.. ] 𓏏𓏏 удивленно поморгав, Даниэль замолчал. снова повисло молчание. он немного задумался, вспоминая их последнюю встречу, как он мог забыть? тот покачал головой, а затем отвел взгляд, не хотелось пристально смотреть на высокую собеседницу. брюнет казался очень низким по сравнению с Ксистер, хотя логично, ведь он младше.. но все еще ощущалось это странновато - стоять с кем-то кто гораздо выше тебя, в к…
Sticker, posted without a caption
Sticker, posted without a caption
[ 🌻 connect.. ] 𓏏𓏏 брюнет стоял молча, осматриваясь на новом для него месте, а затем снова перевел взгляд на девушку за пианино. — видимо, все же заблудился.. — подумал он. просто стоять не вымолвив ни слова было бы глупо, не так ли? — я сам найду дорогу назад.. мы где-то виделись..? вы кажетесь мне знакомыми. 𓏏𓏏 чувство дежавю не отпускало Даниэля, но он решил просто проигнорировать это, спрашивая прямо и не м…
Sticker, posted without a caption
Showing the 12 most recent of 20 posts we hold for @Daniel_dfnet. 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.
Citation-graph rank — 124,606 of 1,169,250entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
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 August 2026 — this entry's latest reading, not the date you are reading this.
“@ 𝖣𝖺𝗇𝗂𝖾𝗅’𝗌 𝗀𝖺𝗋𝖽𝖾𝗇.” (@Daniel_dfnet), 8 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/Daniel_dfnet.
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.