Channel
@FandomOceanFLO
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Polls · Citations · Handles named that no longer answer · Cite this entry
20subscribers
+0 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002506890605 |
|---|---|
| Type | Channel |
| Username | @FandomOceanFLO |
| Created | Between 1 March 2025 and 24 June 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 11 August 2026 |
| Last confirmed live | 11 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/FandomOceanFLO |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 11 Aug 2026, 15:45 | 20 | no change |
| 7 Aug 2026, 16:27 | 20 | first reading |
20 posts held, back to 24 June 2025 — 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.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 20 posts for this entry, the most recent from 9 July 2025. An engagement rate over an empty window would be a number about nothing.
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.
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 20 posts, in 11 distinct kinds. The most used accounts for 61.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🐳 | 36 | 61.0% | |
| custom 5375581432745834952 | 6 | 10.2% | |
| custom 5431369591882273396 | 3 | 5.08% | |
| custom 5431826456143480816 | 3 | 5.08% | |
| 🍓 | 3 | 5.08% | |
| custom 5375518288136652183 | 2 | 3.39% | |
| 💘 | 2 | 3.39% | |
| custom 5249355646746245666 | 1 | 1.69% | |
| custom 5377439916634422055 | 1 | 1.69% | |
| 💔 | 1 | 1.69% | |
| 💯 | 1 | 1.69% |
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 areTelegram’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 20 of the 20 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 59reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 20 most recent posts we hold, published 24 June 2025 to 9 July 2025, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
nêw videoʻ😖 fandom ocean ! #video -- #chaeyoung ➿➿➿➿➿➿➿➿➿➿➿ – давно видео не было конечно.. вступайте к нам скорее!! ➿➿➿➿➿➿➿➿➿➿➿ 🔵по поводу вступления : @unrealssu 🔥давайте много рк !!
🍓3💘2💔1
ЧИСТКА СОЮЗОВ что необходимо сделать: ¹рп себе в инфо ² отметить в комментах: @юз следящего - @юз инфо чистка пройдет до 09.06 отметились: 1. @myxaluv @speedupers 2. @Desw1ht @hanitinfoo 3. @Moonlit_walk @murmurstraw 4. @sonley_lee - @vireis_flood 5. @starmwa - @greenteeinfo 6. @dreamcore_info - @Chris_9728 7. @miossaa - @lionel_f 8. @kimm_muy — @ainix_flood 9. @psixxometrik - @oblivion1_flood 10.…
💯1
ׄㅤ⸝ㅤ⸝ ㅤ) ੭ㅤㅤִㅤ︶⏝ ׄ ㅤ😦 𝓚онкурс 𝘧𝘳. 𝘤𝘩𝘦 𝘤𝘰𝘧𝘧𝘦𝘦 ࿙ᅠ 🐕 ᅠ ۫ ᅠ𓈒 ᅠ ✶͟ᅠ ֺ . – ýслoвuя – подписка на нас ' @checoffeeflood ¹рп в канал / 3 друзьям ²скинуть скрины в коммы ³ждать результатов приз : 🌹 / 🎁 ⏳ Подведение итогов: 12:00 13-07-2025 (Московское время) 🏆 Призовых мест: 1 👤
custom 53755814327458349522
new реакции
custom 54318264561434808163custom 53755182881366521832custom 54313695918822733962custom 52493556467462456661custom 53774399166344220551
кстати подпишитесь на нее, влд очень хорошенькая
🐳2custom 53755814327458349522custom 54313695918822733961
проведем конкурс?
Shares as published, totalling 99%. No per-option vote count is published by Telegram, so none is shown.
custom 53755814327458349522
10<<<<<<180 сзрп
🐳2
🩷🩷🩷🩷 «KÌSS OŔ SĹAP» 𝖿𝗋.𝒞 he 𝒞 offee 1 . подписка на нас 2 . рп другу / в тгк 3 . + в комм 🤩 kiss or slap – [поцелуй или пощечина]. другие люди оценивают ваш профиль реакциями, поцеловали они бы вас или дали пощечину мéста: 0/10 (могут пополняться)
🐳4
приз выдан
🐳4
поздравляем победителя, всем спасибо за участие 🌟
🐳4
🍀 Розыгрыш Конкурс от 𝐅𝐚𝐧𝐝𝐨𝐦 𝐎𝐜𝐞𝐚𝐧 был завершён. 🏆 Поздравляем победителей: 🥇kioshi 🪽. @kioshiii_lol #LR9FG
🐳1
все, делаю итоги
🐳1
Showing the 12 most recent of 20 posts we hold for @FandomOceanFLO. 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.
The 2 polls we hold for this entry, as Telegram rendered them when we read the post. A poll’s figures keep moving after that, so each one is dated.
проведем конкурс?
Shares as published, totalling 99%. No per-option vote count is published by Telegram, so none is shown.
делаю итоги конкурса(сз рп)
Shares as published. No per-option vote count is published by Telegram, so none is shown.
Percentages only — there are no per-option vote counts here, because Telegram publishes none.The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.
The shares need not add up to 100.Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.
Read from the 20 most recent posts we hold, published 24 June 2025 to 9 July 2025. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.
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.
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.
@FandomOceanFLO named 16 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 11 August 2026 — this entry's latest reading, not the date you are reading this.
“𝐅𝐚𝐧𝐝𝐨𝐦 𝐎𝐜𝐞𝐚𝐧//𝐅𝐋𝐎𝐎𝐃” (@FandomOceanFLO), 20 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/FandomOceanFLO.
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.