Telegram RegisterThe public register of Telegram

Channel

FORTUNA

@itzfortuna

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry

120subscribers

+0 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1001556821586
TypeChannel
Username@itzfortuna
Description𝐝𝐦: @fortuna440
CreatedBetween 1 July 2021 and 31 January 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded9 August 2026
Last confirmed live9 August 2026
Measurements held2
On Telegramt.me/itzfortuna

Growth

1207 August 2026 — 120 subscribers9 August 2026 — 120 subscribers7 August 20269 August 2026
2 measurements spanning 2 days. 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 119–121 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
9 Aug 2026, 04:02120no change
7 Aug 2026, 11:50120first reading

Engagement

19 posts held, back to 26 November 2023the 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 19 posts for this entry, the most recent from 22 August 2024. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
31
Videos
88
Links
16

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

Video runtime
9m 00s
Average length
49s

Measured directly from 11 videos 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.

Reaction mix

4,245 reactions across 19 posts, in 42 distinct kinds. The most used accounts for 27.8% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
1,18027.8%
🔥98823.3%
🎉63114.9%
🤩61314.4%
🥰55913.2%
🏆441.04%
350.824%
💯240.565%
❤‍🔥180.424%
🍓170.4%
🆒120.283%
🍾120.283%
100.236%
😍90.212%
👍80.188%
😈70.165%
🍌60.141%
🎃60.141%
🎅50.118%
👏50.118%
22 further kinds561.32%

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 19 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 4,245reactions 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 26 November 2023 to 22 August 2024, 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

22 Aug 2024, 17:36 UTC≈2,010 views6 reactionsread 9 August 2026
Forwarded from @gatororggPhoto

TOP 10 IPAD PLAYERS WORLD 🌎 1) SLIDER 🇯🇴 | SOCLOSE 🇮🇷 DOHA 🇵🇸 | 90 FPS 🇹🇷 2) WATAN🇸🇾| Z3EM 🇱🇧 FRUTELLA 🇷🇺 | KARTAVY 🇷🇺 3) ARTHUR 🇮🇶 | FORTUNA 🇷🇺 BREAK 🇱🇾 | FRIXZI 🇷🇺 4) DEFENDER 🇱🇾 | CHEBA 🇺🇦 5) QEVO 🇪🇬 | ZEUS 🇹🇷 6) GUSTO 🇲🇦 7) FARESS🇲🇦 8) MADARA 🇩🇿 9) HOMY 🇱🇾 10) JORDAN 🇯🇴

3❤‍🔥1🏆1😁1

Signed ᅠᅠᅠ

21 Aug 2024, 16:42 UTC≈1,530 views4 reactionsread 9 August 2026
Forwarded from @tdmempire666Photo

TOP 10 IPAD PLAYERS 🌐 1) SLIDER 🇯🇴 | 90FPS 🇹🇷 2) SERPENT 🇦🇱 | HOMY🇱🇾 3) AMINO 🇱🇾 4) FORTUNA 🇷🇺 5) ZATKNIS 🇺🇦 6) ZEUS 🇹🇷 7) RAID 🇩🇿 8) COURAGE 🇵🇸 9) GUSTO 🇲🇦 10) HIMICO 🇺🇦

🏆31

Signed ᅠᅠᅠ

6 Aug 2024, 15:10 UTC≈1,480 views8 reactionsread 9 August 2026
Forwarded from @RADKA_TOURPhoto

TOP 10 IPAD PLAYERS BY N1 CIS ORGANIZATION🏅 1) CHEBA🇺🇦, FRIXZI🇷🇺, KARTAVYY🇷🇺 2) FORCE🇧🇾, SYREX🇺🇦, FORTE🇺🇦, FORTUNA🇷🇺 3) MERCURI🇺🇦, ZATKNIS🇺🇦, NEKET🇷🇺, F90🇷🇺 4) ADAM4IK🇦🇲, CHAMPION🇺🇦, GENIUS🇺🇦 5) NEFOR🇦🇿, SJUUSH🇺🇦 6) M440🇺🇿, SERB🇷🇺 7) DECIDE🇦🇿 8) FRIGLIZZ🇷🇺 9) XENZY🇷🇺, COURAGE🇵🇸 10) DISARTED🇦🇲

311❤‍🔥1🏆1👍1

Signed ᅠᅠᅠ

5 Jul 2024, 19:00 UTC≈1,820 views21 reactionsread 9 August 2026

hb to me🎂

🎉11🍾53❤‍🔥1😁1

Signed ︎ ︎

5 Jul 2024, 17:56 UTC≈2,740 views31 reactionsread 9 August 2026
Video

𝐯𝐬 𝐋𝐈𝐑𝐎𝐍🇷🇺, 𝟐:𝟎 𝐯𝐬 𝐒𝐀𝐈𝐍𝐋𝐎𝐂𝐊🇰🇬, 𝟏:𝟎

76😘3🍾2🏆2👏2💯2🔥2

Signed ︎ ︎

26 May 2024, 19:21 UTC≈6,990 views3,033 reactionsread 9 August 2026
Video

𝐯𝐬 𝐖𝐎𝐎𝐙𝐘🇺🇦, 𝟏:𝟎 — invicto

641🎉620🤩612🔥591🥰5573🏆3🍾2

Signed ︎ ︎

6 Apr 2024, 17:38 UTC≈6,800 views828 reactionsread 9 August 2026
Video

𝐯𝐬 𝐃𝐄𝐉𝐀𝐕𝐔🇺🇦, 𝟏:𝟎

422🔥378🏆124🍌3💘2🫡2😈2

Signed ︎ ︎

21 Mar 2024, 19:39 UTC≈4,560 views30 reactionsread 9 August 2026
Video

𝐯𝐬 𝐁𝐎𝐎𝐌🇱🇾, 𝟐:𝟎 𝐯𝐬 𝐒𝐖𝐀𝐘🇹🇩, 𝟐:𝟏

❤‍🔥10🍓64🍾2🏆21🌚1💯1

Signed ︎ ︎

1 Mar 2024, 13:27 UTC≈2,440 views11 reactionsread 9 August 2026
Photo

FUNHEZ PLAYS RANKING IPAD 🌍 MARCH 1) SLIDER🇯🇴 | SOCLOSE🇮🇷 | KARTAVYY🇷🇺 | 90FPS🇹🇷 2) BREAK🇱🇾 | FRUTELLA🇷🇺 3) Z3EM🇱🇧 | FORTUNA🇷🇺 | CHEBA🇺🇦 4) FARESS🇲🇦 | HOMY🇱🇾 5) KARA🇱🇾 | KABUS🇸🇾 | SATIVA🇬🇪 6) Z3EM🇸🇾 7) ZATKNIS🇺🇦 | WOZTO🇫🇷 8) AMINO🇱🇾 9) SSTxSTARK🇪🇬 10) BOYKA🇪🇬

8❤‍🔥1🍓1👍1

Signed ︎ ︎

25 Feb 2024, 13:30 UTC≈3,810 views28 reactionsread 9 August 2026
Video

𝐯𝐬 𝐅𝐀𝐑𝐄𝐒𝐒🇲🇦, 𝟏:𝟎

7🏆4💯43😈3💔2🎃1👀1

Signed ︎ ︎

17 Feb 2024, 12:56 UTC≈3,930 views34 reactionsread 9 August 2026
Video

𝐯𝐬 𝐃𝐑𝟑𝐀𝐖𝐄🇸🇾, 𝟑:𝟎

106🏆5💯2😁2😈2😍2🆒2

Signed ︎ ︎

27 Jan 2024, 19:13 UTC≈3,730 views29 reactionsread 9 August 2026
Video

𝐯𝐬 𝐂𝐀𝐏𝐓𝐀𝐈𝐍🇸🇾, 𝟑:𝟎 — чтобы не забывали

9🏆3💯3🔥3🍓2💘2🕊2🤷‍♂2

Signed ︎ ︎

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

Forward network

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.

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

“FORTUNA” (@itzfortuna), 120 subscribers as measured 9 August 2026. Telegram Register, tgregister.com/channel/itzfortuna.

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.