Telegram RegisterThe public register of Telegram
Telegram profile photo for Allblue FX🌏

Channel

Allblue FX🌏

@allbluefx

On this record: Topic · Growth · Engagement · Reactions · Posts · Handles named that no longer answer · Cite this entry

174subscribers

-7 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-1001749788243
TypeChannel
Username@allbluefx
CreatedBetween 1 December 2021 and 19 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live11 October 2026
Measurements held5
Confirmed unchanged2 times, most recently 11 October 2026
On Telegramt.me/allbluefx

Topic

Crypto & trading — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 24 September 2026 and assigned it the closest of 31 fixed categories, at 97% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.

Growth

174181177.57 August 2026 — 181 subscribers8 August 2026 — 181 subscribers24 August 2026 — 180 subscribers17 September 2026 — 178 subscribers1 October 2026 — 174 subscribers7 August 20261 October 2026
5 measurements spanning 55 days, net -7. 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 173–182 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
1 Oct 2026, 02:15174-4
17 Sept 2026, 11:16178-2
24 Aug 2026, 15:48180-1
8 Aug 2026, 12:47181no change
7 Aug 2026, 09:04181first reading

Engagement

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

Reaction mix

21 reactions across 4 posts, in 6 distinct kinds. The most used accounts for 47.6% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🕊1047.6%
🔥314.3%
🙏314.3%
🐳29.52%
🦄29.52%
🫡14.76%

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 4 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 21 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 19 April 2023 to 29 April 2023, 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

29 Apr 2023, 03:15 UTC744 views2 reactionsread 8 August 2026
Photo

Yang mau belajar masih open ya gw bimbing sampe bisa mandiri ga disuapin signal mulu dapet rebate pula🤌 @bayuariy

🦄2

27 Apr 2023, 03:49 UTC801 views3 reactionsread 8 August 2026
Photo

Dah pada bisa mandiri ada yang recovery dari loss 60jt tinggal sisa 20 jt saja hehe

🕊2🐳1

21 Apr 2023, 14:54 UTC804 views12 reactionsread 8 August 2026
Photo

Saya selaku owner Allblue mengucapkan selamat idul fitri 1444 Hijriah, jika ada salah kata, dan sinyal yang tidak akurat juga flexing yang kurang berkenan mohon maaf lahir batin Semoga kita berjumpa dengan Ramadhan dan idulfitri selanjutnya Juga semakin berkah dan tidak mc 🙏🙏

🕊8🙏3🐳1

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

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

“Allblue FX🌏” (@allbluefx), 174 subscribers as measured 1 October 2026. Telegram Register, tgregister.com/channel/allbluefx.

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.