Channel
@Juliver_flood
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry
186subscribers
-8 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002619717425 |
|---|---|
| Type | Channel |
| Username | @Juliver_flood |
| Created | Between 1 March 2025 and 31 July 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 31 August 2026 |
| Measurements held | 6 |
| Confirmed unchanged | 1 time, most recently 31 August 2026 |
| On Telegram | t.me/Juliver_flood |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 31 Aug 2026, 09:04 | 186 | +1 |
| 24 Aug 2026, 19:03 | 185 | -3 |
| 16 Aug 2026, 17:37 | 188 | -5 |
| 8 Aug 2026, 15:21 | 193 | -1 |
| 8 Aug 2026, 11:48 | 194 | no change |
| 7 Aug 2026, 15:49 | 194 | first reading |
19 posts held, back to 13 January 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 19 posts for this entry, the most recent from 18 July 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.
59 reactions across 13 posts, in 6 distinct kinds. The most used accounts for 27.1% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5352939997248905812 | 16 | 27.1% | |
| ☃ | 14 | 23.7% | |
| custom 5399994915914543878 | 13 | 22.0% | |
| custom 5409099164250300234 | 6 | 10.2% | |
| 🎄 | 6 | 10.2% | |
| custom 5258022207849782614 | 4 | 6.78% |
Custom emoji. 4 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 13 of the 19 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 59 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 19 most recent posts we hold, published 13 January 2026 to 18 July 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.
🗝𝐚𝐭𝐭𝐥𝐞 🗝𝐫𝐨𝐟𝐢𝐥𝐞𝐬 𝖻𝗒 𝖬𝖺𝗒𝖻𝖾𝗅 ➿➿➿➿➿➿➿➿➿➿➿➿ 🌟𝗎𝗅𝖾𝗌 ： Рп в инфо Рк (если прем - три) + в комм Будут скрины полного профиля, поэтому не принимаю с рофл авами, совмы и без ав. ➿➿➿➿➿➿➿➿➿➿➿➿ 🌟𝗋𝗂𝗓𝖾 ： 25 зв (с окупом увеличится) 🌟еста 0/10 Участвуют: @llillvs #mblrp , #сзрп
спойлер кидать?)
☃5
рады союзу)
☃1
🍪 “𝔻𝕆 ℕ𝕆𝕋 𝔼ℕ𝕋𝔼ℝ“ 🍪 𝗂𝗌 𝗐𝗋𝗂𝗍𝗍𝖾𝗇 𝗈𝗇 𝗍𝗁𝖾 𝖽𝗈𝗈𝗋𝗐𝖺𝗒 𝗐𝗁𝗒 𝖼𝖺𝗇'𝗍 𝖾𝗏𝖾𝗋𝗒𝗈𝗇𝖾 𝗃𝗎𝗌𝗍 𝗀𝗈 𝖺𝗐𝖺𝗒 💟💟💟 𝖾𝗑𝖼𝖾𝗉𝗍 𝗒𝗈𝗎, 𝗒𝗈𝗎 𝖼𝖺𝗇 𝗌𝗍𝖺𝗒 . . ➿🎀➿🎀➿🎀➿🥹🥹➿🎀➿🎀➿ ꒰ ꒰ @vinovix && @Juliver_flood ꒱
☃1
#szrp
☃1
𝑱𝑼𝑳𝑰𝑽𝑬𝑹... 𝑪𝑶𝑴𝑬𝑩𝑨𝑪𝑲?... да, мы официально вернулись! набор в нашу семью открыт и ждет только вас, кисы. по поводу набора @MA30NM
☃2🎄1
уважаемые союзники, все кто не разорвал союз, отметьтесь ниже пожалуйста. юз проекта юз следящего подписка #сзрп
☃2🎄1
здравствуйте, все кто ждал от нас информацию. мы живы, однако теперь джюливер имеют нового владельца. меня зовут миллер, я буду продолжать вести этот флуд.
☃2🎄1
флуд уходит в ресте на месяц🤩 вскоре вернёмся с новой эрой и сделаем перенабор участников и админов 🌿 набор нью и союзов закрыт. рп делать не будем, союзы просим не разрывать так как потом перезаключать не будем ᅠᅠᅠᅠᅠᅠᅠᅠ #𝑺𝒛𝑹𝒑🎀🎀🎀
custom 53529399972489058125custom 54090991642503002342
Sticker, posted without a caption
🎄🎄˖ ° 🔤𝑒𝑤 🔤𝑛𝑖𝑜𝑛 ୧ ˖ֹ🎄🎄 🤩🤩🤩🤩🤩🤩🤩🤩🤩🤩🤩 🎄🎄 ( 🤩 ) 𝒋𝒖𝒍𝒊𝒗𝒆𝒓 🎄🎄 ➿➿➿➿➿➿➿➿➿ ♡۪⃕ 🎄 ʚ --- сегодняшней новогодней ночью в 24.01, под бой курантов заключили союз два чудных флуда : 🎅🎅🎅 🎅🎅🎅 @Juliver_flood & @wabisaflood 🎅🎅🎅 彡 🤩 🔤appy New Year! 🤩ミ
custom 53529399972489058124custom 53999949159145438783
Sticker, posted without a caption
Showing the 12 most recent of 19 posts we hold for @Juliver_flood. 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.
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.
@Juliver_flood named 2 handles that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
References a handle that is not a live channel — we have no record it ever was one.
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 31 August 2026 — this entry's latest reading, not the date you are reading this.
“٠࣪ ℐʋ𝗅𝕚𝗏ꫀ𝗋 🔒” (@Juliver_flood), 186 subscribers as measured 31 August 2026. Telegram Register, tgregister.com/channel/Juliver_flood.
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.