Telegram RegisterThe public register of Telegram

Channel

𝗜𝗡𝗙𝗢 | 𝑶𝒗𝒆𝒓 𝑯𝒆𝒂𝒗𝒆𝒏

@WeOverHeaven

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry

28subscribers

+0 since we began measuring on 10 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1004392222283
TypeChannel
Username@WeOverHeaven
DescriptionThe sky is not the limit
Created17 July 2026measured — dated from the channel’s first post
First recorded11 August 2026
Last confirmed live11 August 2026
Measurements held2
On Telegramt.me/WeOverHeaven

Growth

2810 Aug 2026, 20:47 — 28 subscribers11 Aug 2026, 06:17 — 28 subscribers10 Aug 2026, 20:4711 Aug 2026, 06:17
2 measurements taken within a single day. 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 27–29 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
11 Aug 2026, 06:1728no change
10 Aug 2026, 20:4728first reading

Engagement

12 posts held, back to 17 July 2026the 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 · 30 days
578.9%
avg views ÷ 28 subscribers
Avg views / post
162
11 posts measured
Reaction rate
5.95%
reactions ÷ views · ER floor
Posts in window
12
of 12 held

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.

What these figures were computed from
WindowRolling 30 days · latest post in window 7 August 2026
Posts held12 (17 July 20267 August 2026)
Views total1,783
Reactions total106
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken11 Aug 2026, 06:17 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.

What this channel posts

Photos
1
Links
5

Lifetime counters from Telegram’s own channel header, read 11 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.

Reaction mix

106 reactions across 11 posts, in 17 distinct kinds. The most used accounts for 28.3% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
3028.3%
🥰3028.3%
❤‍🔥1211.3%
💋98.49%
🤗87.55%
🍓43.77%
🙉21.89%
🤪21.89%
🌭10.943%
👏10.943%
👾10.943%
💘10.943%
💯10.943%
😁10.943%
😇10.943%
🤓10.943%
🦄10.943%

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 11 of the 12 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 106reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 12 most recent posts we hold, published 17 July 2026 to 7 August 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.

Recent posts

7 Aug 2026, 17:11 UTC33 views5 reactionsread 11 August 2026

К концу следующей недели ожидается перенабор участников! У большинства отсутствует актив, посещение съемок сводиться к нулю. Прошу всех отнестись с понимаем к данному решению. с уважением администрация.

🤪2🙉2💘1

2 Aug 2026, 11:29 UTC93 views1 reactionsread 11 August 2026

🤩𝑁𝑢𝑚𝑏𝑒𝑟 𝑜𝑓 𝑝𝑎𝑟𝑡𝑖𝑐𝑖𝑝𝑎𝑛𝑡𝑠 🤩🤩🤩 🤩ᴋᴏᴧичᴇᴄᴛʙᴏ ʏчᴀᴄᴛнᴎᴋᴏʙ - 29/∞

👾1

17 Jul 2026, 08:09 UTC213 views15 reactionsread 11 August 2026

🤩𝑇𝑖𝑘𝑇𝑜𝑘 𝐶𝑙𝑎𝑛 🤩🤩🤩 🤩нᴀɯ ᴛиᴋ ᴛоᴋ - clan.over.heaven 🤩будᴇʍ ᴩᴀды ʙᴀɯᴇй ᴨодᴨиᴄᴋи 🤩

5💋4🥰4🤗2

17 Jul 2026, 08:07 UTC207 views15 reactionsread 11 August 2026

🤩𝐷𝑠 𝑠𝑒𝑟𝑣𝑒𝑟 🤩🤩🤩 ᴩᴇɯиᴧи дᴧя удобᴄᴛʙᴀ ᴄоздᴀᴛь диᴄᴋоᴩд ᴄᴇᴩʙᴇᴩ! ᴄᴇᴩʙᴇᴩ ᴄоздᴀн дᴧя ᴨᴩоʙᴇдᴇния ᴄъᴇʍоᴋ, ʙ ᴛᴦ зʙоноᴋ ᴧᴀᴦᴀᴇᴛ и нᴇ ɸунᴋциониᴩуᴇᴛ. ʙᴄᴛуᴨᴧᴇниᴇ нᴀ ᴄᴇᴩʙᴇᴩ обязᴀᴛᴇᴧьно, нᴀʍ будᴇᴛ нᴇ удобно объяᴄняᴛь ʙᴀʍ чᴛо ᴧибо ʙ ᴛᴇᴋᴄᴛоʙоʍ ɸоᴩʍᴀᴛᴇ. ʙ диᴄᴋоᴩд ᴄᴇᴩʙᴇᴩ ᴋидᴀᴛь зᴀᴨᴩоᴄ ᴛоᴧьᴋо ᴨоᴄᴧᴇ ʙᴄᴛуᴨᴧᴇния ʙ ᴋᴧᴀн!!! 🤩ᴄᴄыᴧᴋᴀ нᴀ диᴄᴋоᴩд ᴄᴇᴩʙᴇᴩ

🥰64❤‍🔥3🤗2

17 Jul 2026, 07:57 UTC199 views13 reactionsread 11 August 2026

🪽 𝐹𝑖𝑙𝑚𝑖𝑛𝑔 𝑠𝑐ℎ𝑒𝑑𝑢𝑙𝑒 🤩🤩🤩 1. нᴀ ᴄъᴇʍᴋᴀх зᴀᴨᴩᴇщᴇно бᴀᴧоʙᴀᴛьᴄя, ᴨиᴄᴀᴛь ᴄообщᴇния и ʙᴄячᴇᴄᴋи ʍᴇɯᴀᴛь! ϶ᴛо нᴀᴋᴀзуᴇʍо. 2. ᴨᴇᴩᴇд нᴀчᴀᴧоʍ ᴄъᴇʍоᴋ нужно зᴀйᴛи ʙ ᴦоᴧоᴄоʙой чᴀᴛ ʙ дᴄ, ᴧибо жᴇ иᴦᴩᴀᴛь ᴄ ʙᴋᴧючᴇнныʍ зʙуᴋоʍ. ᴛᴀᴋ, нᴀʍ будᴇᴛ ᴨᴩощᴇ объяᴄняᴛь ʙᴀʍ чᴛо и ᴋᴀᴋ дᴇᴧᴀᴛь! 3. ᴨᴇᴩᴇд ᴄъᴇʍᴋᴀʍи ᴛᴀᴋ жᴇ обязᴀᴛᴇᴧьно нужно ознᴀᴋоʍиᴛᴄя ᴄ ʙидᴇо ɸᴩᴀᴦʍᴇнᴛоʍ ᴋоᴛоᴩый ʍы будᴇʍ ᴄниʍᴀᴛь. (ʙ зᴀᴋᴩᴇᴨᴇ) 3️⃣ 🔠🔠🔠🔠🔠🔠🔠🔠 ➖

5🥰4❤‍🔥3🤗1

17 Jul 2026, 07:56 UTC175 views14 reactionsread 11 August 2026

—•𝐼𝑛𝑎𝑐𝑡𝑖𝑣𝑒 𝑙𝑖𝑠𝑡 —• Рᴇᴄᴛ - ᴄ ᴀнᴦᴧийᴄᴋᴏᴦᴏ «ᴏᴛдых». Выдᴀчᴀ ᴩᴇᴄᴛᴀ ᴏᴄʙᴏбᴏждᴀᴇᴛ ʙᴀᴄ ᴏᴛ ᴀᴋᴛиʙᴀ и чиᴄᴛᴏᴋ нᴀ ᴏᴨᴩᴇдᴇᴧᴇннᴏᴇ ʙᴩᴇʍя. Мᴀᴋᴄиʍᴀᴧьный ᴄᴩᴏᴋ - 2 нᴇдᴇᴧи ᴄ инᴛᴇᴩʙᴀᴧᴏʍ ʙ 1 нᴇдᴇᴧю. —• Дᴧя ᴛᴏᴦᴏ чᴛᴏ бы ᴨᴏᴧучиᴛь ᴩᴇᴄᴛ ʙы ɜᴀᴨᴏᴧняᴇᴛᴇ ʍини ᴀнᴋᴇᴛу ʙ ᴋᴏʍʍᴇнᴛᴀᴩиях ᴏᴨᴏʙᴇщᴀя ᴏб ϶ᴛᴏʍ ʙᴧᴀдᴇᴧьцᴀ/ᴀдʍинᴏʙ. Бᴩᴀᴛь ᴩᴇᴄᴛ ɜᴀ дᴇнь и ʙ дᴇнь чиᴄᴛᴋи ɜᴀᴨᴩᴇщᴇнᴏ! Оᴨᴏʙᴇщᴀйᴛᴇ ᴏб ϶ᴛᴏʍ ɜᴀᴩᴀнᴇᴇ Пᴩиʍᴇᴩ: 1. Юɜ 2. Дᴀᴛᴀ (дᴏ ᴋᴀᴋᴏᴦᴏ чиᴄᴧᴀ) 3. Пᴩичину (нᴇ ᴏбяɜᴀ

🥰5🍓43💋2

17 Jul 2026, 07:53 UTC194 views13 reactionsread 11 August 2026

🤩𝑄𝑢𝑒𝑠𝑡𝑖𝑜𝑛𝑛𝑎𝑖𝑟𝑒 ʙᴀжно: 1. ʍы нᴇ ᴨᴩиниʍᴀᴇʍ ʙ ᴋᴧᴀн ᴧюдᴇй ᴄ ᴛᴩоᴧᴧ ᴄᴋинᴀʍи. 2. нᴇ ᴨᴩиниʍᴀᴇʍ ᴧюдᴇй ᴄ ᴧʙᴧ нижᴇ 30! 3. нᴀᴧичиᴇ диᴄᴋоᴩдᴀ (иᴧи ᴇᴄᴧи ʙы нᴇ ʙ ᴩоᴄᴄии ᴛо ʙойᴄ чᴀᴛ) ʙ нᴀɯᴇʍ ᴋᴧᴀнᴇ обязᴀᴛᴇᴧьно. 4. ᴨᴩи одобᴩᴇнии зᴀяʙᴋи доᴧжны знать что вы должны ᴀᴋᴛиʙиᴛь и учᴀᴄᴛʙоʙᴀᴛь ʙ жизни ᴋᴧᴀнᴀ ᴨᴩиʍᴇᴩ ᴀнᴋᴇᴛы 1. ʙᴀɯᴇ иʍя, ᴨᴄᴇʙдониʍ иᴧи жᴇ ᴋᴧичᴋᴀ. (ʙᴄᴇ ᴄᴩᴀзу ᴋонᴇчно жᴇ ʍожно) — 2. ʙозᴩᴀᴄᴛ. (14+) — 3. ниᴋ ʙ ᴩобᴧоᴋᴄᴇ. — 4. ᴄᴋин.

❤‍🔥43💋3🥰3

17 Jul 2026, 07:50 UTC170 views10 reactionsread 11 August 2026

🤩𝐶𝑙𝑒𝑎𝑛𝑖𝑛𝑔 🤩чиᴄᴛᴋᴀ- ʙᴩᴇʍя удᴇᴧᴇнноᴇ дᴧя удᴀᴧᴇния нᴇ ᴀᴋᴛиʙных учᴀᴄᴛниᴋоʙ бᴇз ноᴩʍы. 🤩ноᴩʍᴀ - нужноᴇ ᴋоᴧичᴇᴄᴛʙо ᴄообщᴇний зᴀ нᴇдᴇᴧю. 🤩ʍы ʍожᴇʍ зᴀᴄчиᴛᴀᴛь ноᴩʍу ᴄ диᴄᴋоᴩдᴀ ᴇᴄᴧи ʙы чᴀᴄᴛо ᴀᴋᴛиʙиᴛᴇ ᴛᴀʍ 🤩🤩🤩 чиᴄᴛᴋᴀ ᴨᴩоʙодиᴛᴄя ʙ ʙоᴄᴋᴩᴇᴄᴇньᴇ, ʙᴩᴇʍя оᴨᴩᴇдᴇᴧяᴇᴛᴄя ʙ ᴛᴇчᴇнии ʙᴄᴇᴦо дня. ноᴩʍᴀ ᴄообщᴇний - 150 зᴀ нᴇдᴇᴧю!

🥰42❤‍🔥2💯1🤗1

17 Jul 2026, 07:47 UTC166 views8 reactionsread 11 August 2026

🤩𝑅𝑢𝑙𝑒𝑠 дᴧя нᴀɯᴇᴦо ᴋᴧᴀнᴀ быᴧи ᴄоᴄᴛᴀʙᴧᴇны ᴨᴩᴀʙиᴧᴀ ᴋоᴛоᴩыᴇ доᴧжны ᴄобᴧюдᴀᴛь ʙᴄᴇ (дᴀжᴇ ᴀдʍины) 𝑅𝑢𝑙𝑒𝑠 𝑃.𝑆 ᴄᴄыᴧᴋᴀ нᴀ ᴨᴩᴀʙиᴧᴀ ᴋᴧиᴋᴀбᴇᴧьнᴀ и обязᴀᴛᴇᴧьны дᴧя ᴨᴩочᴛᴇния ᴇᴄᴧи ʙы хоᴛиᴛᴇ ʙᴄᴛуᴨиᴛь нᴀɯ ᴋᴧᴀн

3🥰3🤗2

17 Jul 2026, 07:42 UTC173 views7 reactionsread 11 August 2026

𝐶𝑙𝑎𝑛 𝑐𝑜𝑚𝑝𝑜𝑠𝑖𝑡𝑖𝑜𝑛 🤍 🤩 ʙᴧᴀдᴇᴧᴇц - @LordOfGeneration #Сули 🤩ᴄᴛᴀᴩший ᴀдʍин - @kkwwksn #кейко 🤩 ʍᴧᴀдɯий ᴀдʍин - @reswweq #балтика 🤩 диᴄᴋоᴩд ᴀдʍин - @k0tiukcc #мур 🤩 диᴄᴋоᴩд ᴀдʍин - @mortyshkss #мартышка 🤩 ʍонᴛᴀжёᴩ - #цветкова 🤩 оᴨᴇᴩᴀᴛоᴩ - #цветкова

2👏1🥰1🦄1😁1😇1

17 Jul 2026, 07:41 UTC160 views5 reactionsread 11 August 2026
Photo

🤩𝑁𝑎𝑣𝑖𝑔𝑎𝑡𝑖𝑜𝑛🤩 🤩𝑅𝑢𝑙𝑒𝑠 🤩𝑄𝑢𝑒𝑠𝑡𝑖𝑜𝑛𝑛𝑎𝑖𝑟𝑒 🤩𝐶𝑙𝑒𝑎𝑛𝑖𝑛𝑔 🤩𝐶𝑙𝑎𝑛 𝑐𝑜𝑚𝑝𝑜𝑠𝑖𝑡𝑖𝑜𝑛 🤩𝐹𝑖𝑙𝑚𝑖𝑛𝑔 𝑠𝑐ℎ𝑒𝑑𝑢𝑙𝑒 🤩𝐼𝑛𝑎𝑐𝑡𝑖𝑣𝑒 𝑙𝑖𝑠𝑡 🤩𝑇𝑖𝑘𝑇𝑜𝑘 𝐶𝑙𝑎𝑛 🤩𝐷𝑠 𝑠𝑒𝑟𝑣𝑒𝑟 🤩𝑁𝑢𝑚𝑏𝑒𝑟 𝑜𝑓 𝑝𝑎𝑟𝑡𝑖𝑐𝑖𝑝𝑎𝑛𝑡𝑠

3🌭1🤓1

Showing the 12 most recent of 12 posts we hold for @WeOverHeaven. 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

Citation-graph rank — 778,980 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.

Mentions

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.

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 11 August 2026 — this entry's latest reading, not the date you are reading this.

“𝗜𝗡𝗙𝗢 | 𝑶𝒗𝒆𝒓 𝑯𝒆𝒂𝒗𝒆𝒏” (@WeOverHeaven), 28 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/WeOverHeaven.

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.