Telegram RegisterThe public register of Telegram

Channel

◜ 𝓵𝗈𝗅𝗅𝖺𝗽𝖺𝗅𝗈𝗈𝘇𝗮 ◞

@paloozarp

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

96subscribers

+1 since we began measuring on 12 August 2026

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

Register entry

Telegram ID-1002338144933
TypeChannel
Username@paloozarp
CreatedBetween 1 September 2024 and 31 March 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded12 August 2026
Last confirmed live13 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 13 August 2026
On Telegramt.me/paloozarp

Growth

959695.512 Aug 2026, 09:03 — 95 subscribers12 Aug 2026, 09:15 — 95 subscribers13 Aug 2026, 04:14 — 96 subscribers12 Aug 2026, 09:0313 Aug 2026, 04:14
3 measurements taken within a single day, net +1. 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 95–96 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
13 Aug 2026, 04:1496+1
12 Aug 2026, 09:1595no change
12 Aug 2026, 09:0395first reading

Engagement

20 posts held, back to 7 April 2025the 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 27 April 2025. An engagement rate over an empty window would be a number about nothing.

Reaction mix

137 reactions across 9 posts, in 13 distinct kinds. The most used accounts for 21.9% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
3021.9%
🔥2014.6%
🥰2014.6%
❤‍🔥1510.9%
👏128.76%
🎉96.57%
🍾75.11%
🏆64.38%
👍53.65%
🤩53.65%
💯42.92%
😎21.46%
🤪21.46%

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 9 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 137reactions 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 7 April 2025 to 27 April 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.

Recent posts

27 Apr 2025, 14:46 UTC≈1,900 views29 reactionsread 12 August 2026

⁣⁣⁣⁣⁣ᅟᅟᅟᅟᅟᅟ 🤩﹐𝖤 𝖺ı‌, 𝖺𝗆𝗈𝗋𝖾𝗌! 𝖢𝗁𝖾𝗀𝖺𝗆𝗈𝗌 𝖺𝗈 𝖿𝗂𝗇𝖺𝗅 𝖽𝗈𝗌 𝗇𝗈𝗌𝗌𝗈𝗌 𝗊𝗎𝖺𝗍𝗋𝗈 𝖽𝗂𝖺𝗌 𝗆𝖺‌𝗀𝗂𝖼𝗈𝗌 𝖽𝖾 𝖿𝖾𝗌𝗍𝗂𝗏𝖺𝗅, 𝖾 𝖺 𝗌𝖺𝗎𝖽𝖺𝖽𝖾 𝗃𝖺‌ 𝖻𝖺𝗍𝖾 𝖿𝗈𝗋𝗍𝖾! 𝖭𝗈‌𝗌, 𝖽𝖺 𝖺𝖽𝗆𝗂𝗇𝗂𝗌𝗍𝗋𝖺𝖼‌𝖺‌𝗈 @spicyzs, @mothrcain, @versacrz, 𝗊𝗎𝖾𝗋𝖾𝗆𝗈𝗌 𝖺𝗀𝗋𝖺𝖽𝖾𝖼𝖾𝗋 𝖽𝖾 𝖼𝗈𝗋𝖺𝖼‌𝖺‌𝗈 𝖺 𝖼𝖺𝖽𝖺 𝗎𝗆 𝖽𝖾 𝗏𝗈𝖼𝖾‌𝗌 𝗉𝖾𝗅𝖺 𝗉𝗋𝖾𝗌𝖾𝗇𝖼‌𝖺 𝖾 𝗉𝗈𝗋 𝖿𝖺𝗓𝖾𝗋 𝗉𝖺𝗋𝗍𝖾 𝖽𝖾𝗌𝗌𝖺 𝗏𝗂𝖻𝖾 𝗆𝖺𝗋𝖺𝗏𝗂𝗅𝗁𝗈𝗌𝖺. 𝖴𝗆 𝖺𝗀𝗋𝖺𝖽𝖾𝖼𝗂𝗆𝖾𝗇𝗍𝗈 𝖾𝗌𝗉𝖾𝖼𝗂𝖺𝗅 𝖺𝗈𝗌 𝗇𝗈𝗌𝗌𝗈𝗌 𝖺𝗋𝗍𝗂𝗌𝗍𝖺𝗌 𝗂𝗇𝖼𝗋ı‌𝗏𝖾𝗂𝗌, 𝗊𝗎𝖾 𝖻𝗋𝗂𝗅𝗁𝖺𝗋𝖺𝗆 𝖾 𝖾𝗇𝗍𝗋𝖾𝗀𝖺𝗋𝖺𝗆 𝗉𝖾𝗋𝖿𝗈𝗋𝗆𝖺𝗇𝖼𝖾𝗌 𝖾𝗌𝗉𝖾𝗍𝖺𝖼𝗎𝗅𝖺𝗋𝖾𝗌. 𝖵𝗈𝖼𝖾‌𝗌 𝖿𝗈𝗋𝖺𝗆 𝖺 𝖺𝗅𝗆𝖺

13👏6🥰6❤‍🔥3👍1

25 Apr 2025, 22:56 UTC≈1,910 views1 reactionsread 12 August 2026

⁣⁣⁣⁣⁣ᅟᅟᅟᅟᅟᅟ 🤩﹐𝖤𝗆 𝗂𝗇𝗌𝗍𝖺𝗇𝗍𝖾𝗌 𝖽𝖺𝗋𝖾𝗆𝗈𝗌 𝗂𝗇ı‌𝖼𝗂𝗈 𝖺 𝗌𝖾𝗀𝗎𝗇𝖽𝖺 𝗌𝖾𝗆𝖺𝗇𝖺 𝖽𝖾 𝖫𝗈𝗅𝗅𝖺𝗉𝖺𝗅𝗈𝗈𝗓𝖺! 𝖭𝖠‌𝖮 𝖯𝖤𝖱𝖢𝖠𝖬! 𝖫𝖾𝗆𝖻𝗋𝖾𝗆-𝗌𝖾: 𝗌𝖾 𝗏𝗈𝖼𝖾‌ 𝗇𝖺‌𝗈 𝖿𝗈𝗋, 𝗌𝗈‌ 𝗏𝗈𝖼𝖾‌ 𝗇𝖺‌𝗈 𝗏𝖺𝗂! ✨ ᅟᅟᅟᅟᅟᅟ

1

17 Apr 2025, 22:42 UTC≈3,840 viewsread 12 August 2026

⁣⁣⁣ᅟᅟᅟᅟᅟᅟ 🤩﹐𝖯𝖱𝖤𝖯𝖠𝖱𝖠𝖣𝖤𝖲 𝖯𝖠𝖱𝖠 𝖮 𝖯𝖱𝖨𝖬𝖤𝖨𝖱𝖮 𝖣𝖨𝖠? 𝖬𝖺𝗅 𝗉𝗈𝖽𝖾𝗆𝗈𝗌 𝖾𝗌𝗉𝖾𝗋𝖺𝗋 𝗉𝖺𝗋𝖺 𝗏𝖾𝗋 𝖼𝖺𝖽𝖺 𝗎𝗆 𝖽𝖾 𝗏𝗈𝖼𝖾‌𝗌 𝗅𝖺‌, 𝗏𝖺𝗂 𝗌𝖾𝗋 𝗆𝖺‌𝗀𝗂𝖼𝗈! 𝖮 𝖫𝖮𝖫𝖫𝖠 𝖢𝖮𝖬𝖤𝖢‌𝖠 𝖠𝖬𝖠𝖭𝖧𝖠‌! ✨ ᅟᅟᅟᅟᅟᅟ

7 Apr 2025, 16:17 UTC≈1,790 views15 reactionsread 12 August 2026

⁣⁣⁣⁣ᅟᅟᅟᅟᅟᅟ ◜ 𝓵𝗈𝗅𝗅𝖺𝗽𝖺𝗅𝗈𝗈𝘇𝗮 ◞ lineup 𝓞f April 26th ⋆ 𝗉𝖺𝗅𝗈𝗈︩︪𝗓𝖺𝗋𝗉 ᅟᅟᅟᅟᅟᅟ

🎉54🥰3👏2🔥1

7 Apr 2025, 16:16 UTC≈1,250 views13 reactionsread 12 August 2026

⁣⁣⁣⁣ᅟᅟᅟᅟᅟᅟ ◜ 𝓵𝗈𝗅𝗅𝖺𝗽𝖺𝗅𝗈𝗈𝘇𝗮 ◞ lineup 𝓞f April 26th ⋆ 𝗉𝖺𝗅𝗈𝗈︩︪𝗓𝖺𝗋𝗉 ᅟᅟᅟᅟᅟᅟ

❤‍🔥53🔥3🥰2

7 Apr 2025, 16:15 UTC≈1,450 views37 reactionsread 12 August 2026

⁣⁣⁣⁣ᅟᅟᅟᅟᅟᅟ ◜ 𝓵𝗈𝗅𝗅𝖺𝗽𝖺𝗅𝗈𝗈𝘇𝗮 ◞ lineup 𝓞f April 26th ⋆ 𝗉𝖺𝗅𝗈𝗈︩︪𝗓𝖺𝗋𝗉 ᅟᅟᅟᅟᅟᅟ

🔥85❤‍🔥4🍾4🏆3👏3👍2🤩2

Showing the 12 most recent of 20 posts we hold for @paloozarp. 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 — 386,666 of 1,345,403entries 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.

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.

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

“◜ 𝓵𝗈𝗅𝗅𝖺𝗽𝖺𝗅𝗈𝗈𝘇𝗮 ◞” (@paloozarp), 96 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/paloozarp.

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.