Channel
@authortemple
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
220subscribers
+0 since we began measuring on 10 November 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002272933975 |
|---|---|
| Type | Channel |
| Username | @authortemple |
| Created | Between 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 10 November 2026 |
| Last confirmed live | 11 November 2026 |
| Measurements held | 2 |
| Confirmed unchanged | 1 time, most recently 11 November 2026 |
| On Telegram | t.me/authortemple |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 11 Nov 2026, 12:10 | 220 | no change |
| 10 Nov 2026, 17:22 | 220 | first reading |
16 posts held, back to 13 October 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.
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. It is computed over the 12 of 14 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 10 November 2026 |
|---|---|
| Posts held | 16 (13 October 2026 – 10 November 2026) |
| Views total | 1,863 |
| Reactions total | 454 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 10 Nov 2026, 17:22 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.
519 reactions across 14 posts, in 16 distinct kinds. The most used accounts for 21.2% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5212987504361230388 | 110 | 21.2% | |
| custom 5456168638560093886 | 77 | 14.8% | |
| custom 5226837794638276282 | 63 | 12.1% | |
| custom 5107105183146443823 | 58 | 11.2% | |
| custom 5260675776084217979 | 58 | 11.2% | |
| custom 5339236461709392592 | 35 | 6.74% | |
| 🥰 | 31 | 5.97% | |
| 🔥 | 27 | 5.20% | |
| custom 5409374587618101733 | 22 | 4.24% | |
| 😈 | 14 | 2.70% | |
| 🎃 | 10 | 1.93% | |
| custom 5458569078601964113 | 9 | 1.73% | |
| 💔 | 2 | 0.385% | |
| 💘 | 1 | 0.193% | |
| 😭 | 1 | 0.193% | |
| 🫡 | 1 | 0.193% |
Custom emoji. 8 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 14 of the 16 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 519 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 16 most recent posts we hold, published 13 October 2026 to 10 November 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.
Telegram’s own ‘edited’ marker: 0 of 14 posts held from the last 30 days (0%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).
✅ты художник?💖 не знаешь где найти аудиторию,или единомышленников? 🌷 @piarartist - канал для пиара твоего тг творчества 💗 Автор арта 💕💕 💖@geshaxaxa 💖
custom 52606757760842179791
Sticker, posted without a caption
Что за разбитые сердца ай ай.
🫡1
🔤🔤🔤🔤🔤🔤🔤🔤🔤🔤💙 💙💙 #скетч@authortemple #коммишен@authortemple
custom 540937458761810173313custom 52268377946382762828custom 54561686385600938864💔2😭1
🤷♀ Пытаюсь заспидранить крипоту на конкурс.
custom 522683779463827628211custom 526067577608421797911custom 51071051831464438235custom 54561686385600938863
🔤🔤🔤🔤🔤🔤🔤🔤🔤🔤💙 💙💙 ✨ #коммишен@authortemple
custom 545616863856009388620custom 526067577608421797910custom 52268377946382762826
#wip 💅
custom 533923646170939259226custom 526067577608421797915custom 52268377946382762827custom 54561686385600938863
Артов тематических не будет но счастливого Халовина) 🤩
🎃10custom 54585690786019641136custom 52606757760842179794
🤩🤩🤩🤩🤩⭐ 🤩🤩🤩🤩🤩🤩🤩 🤩🤩🤩 🌟 Победитель: @JIYTR1 💙Поздравляю с выигрышем!💙 💙 Приз: полноценный хэд арт. Прошу ответить мне в лс для дальнейшего обсуждения)
custom 54093745876181017339custom 54561686385600938865custom 52606757760842179793custom 51071051831464438231
В 12:30(мск) будут итоги⭐
Posted without readable text
custom 521298750436123038832😈14custom 522683779463827628210custom 52606757760842179795
🔤🔤🔤🔤🔤🔤🔤🔤🔤🔤💙 💙💙 🌙 #коммишен@authortemple
custom 521298750436123038843custom 510710518314644382317custom 545616863856009388615custom 52606757760842179793
Showing the 12 most recent of 16 posts we hold for @authortemple. 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.
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.
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.
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.
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 11 November 2026 — this entry's latest reading, not the date you are reading this.
“✧ ʟᴀᴛᴛᴇᴛᴇᴀᴍᴏ | Храм разума” (@authortemple), 220 subscribers as measured 11 November 2026. Telegram Register, tgregister.com/channel/authortemple.
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.