Channel
@fantom_detailing
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
109subscribers
+8 since we began measuring on 23 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003833398192 |
|---|---|
| Type | Channel |
| Username | @fantom_detailing |
| Created | Between 1 February 2026 and 2 June 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 23 August 2026 |
| Last confirmed live | 1 September 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 1 September 2026 |
| On Telegram | t.me/fantom_detailing |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 1 Sept 2026, 11:25 | 109 | +6 |
| 24 Aug 2026, 21:17 | 103 | +2 |
| 23 Aug 2026, 08:45 | 101 | first reading |
4 posts held, back to 2 June 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 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 4 posts for this entry, the most recent from 30 June 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 1 video with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.
43 reactions across 4 posts, in 8 distinct kinds. The most used accounts for 46.5% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5458908492687497206 | 20 | 46.5% | |
| custom 5377337558973817602 | 7 | 16.3% | |
| custom 5285439518130857782 | 4 | 9.30% | |
| custom 5350702035819833989 | 3 | 6.98% | |
| custom 5852698513455976397 | 3 | 6.98% | |
| custom 5449505950283078474 | 2 | 4.65% | |
| ❤ | 2 | 4.65% | |
| 👍 | 2 | 4.65% |
Custom emoji. 6 of the rows above are 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 counts beside them are 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 4 of the 4 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 43 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 4 most recent posts we hold, published 2 June 2026 to 30 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.
Выполнен комплекс услуг для Mazda CX-8 🫧Глубокая полировка + нанесение защитного керамического покрытия в 2 слоя ⚫️Локальный окрас (удаление потертостей кузова) 💧Влажная уборка салона Мы находимся по адресу: г. Владивосток, ул. Никифорова 4 (р-н Тихая) Ждём вас для записи и консультации @fantom_detail📩
custom 54589084926874972066custom 53773375589738176023custom 52854395181308577822
Выполнен комплекс услуг для Honda Freed 🫧Глубокая полировка + нанесение защитного керамического покрытия в 2 слоя 🔵Локальный окрас (удаление глубоких царапин) ◻️Защита зон риска под ручками полиуретановой защитной пленкой ⬛️Тонировка задней полусферы 💧Влажная уборка салона Мы находимся по адресу: г. Владивосток, ул. Никифорова 4 (р-н Тихая) Ждём вас для записи и консультации @fantom_detail📩
custom 54589084926874972065custom 52854395181308577822custom 53773375589738176022custom 54495059502830784742
Мы наслаждаемся работой 🤟🏻 Вы наслаждаетесь результатом 🔥
custom 54589084926874972066custom 58526985134559763973custom 53507020358198339892
Полировка всего кузова + керамика — это не просто «блеск», а полное преображение вашего авто Перед нанесением керамики мы работаем точечно: устраняем локальные дефекты ЛКП — царапины, потёртости, следы от мойки. Только потом – финишная полировка и защита. 🔹 Что делаем: – локальная коррекция лака – глубокая полировка по всей площади – нанесение керамики с гидрофобным эффектом 💎 Результат: – зеркальный блеск – защит…
custom 54589084926874972063❤2👍2custom 53773375589738176022custom 53507020358198339891
Showing the 4 most recent of 4 posts we hold for @fantom_detailing. 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 — 1,343,520 of 1,629,808 entries 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 1 September 2026 — this entry's latest reading, not the date you are reading this.
“Фантом Dетейлинг” (@fantom_detailing), 109 subscribers as measured 1 September 2026. Telegram Register, tgregister.com/channel/fantom_detailing.
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.