Channel

لــ حمو التركي

@PS_SPZ

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

22subscribers

+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	-1003070044935
Type	Channel
Username	@PS_SPZ
Created	6 September 2025 — measured — dated from the channel’s first post
First recorded	11 August 2026
Last confirmed live	11 August 2026
Measurements held	2
On Telegram	t.me/PS_SPZ

Growth

2 measurements spanning 4 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 21–23 and does not start at zero.

Measurement log — every subscribers count we have recorded
Measured (UTC)	Subscribers	Change
11 Aug 2026, 13:04	22	no change
7 Aug 2026, 20:18	22	first reading

Engagement

3 posts held, back to 6 September 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 3 posts for this entry, the most recent from 1 October 2025. An engagement rate over an empty window would be a number about nothing.

Reaction mix

45 reactions across 2 posts, in 10 distinct kinds. The most used accounts for 20.0% of them.

Every reaction kind recorded on the sample, most used first
Reaction	Count	Share
custom 5400273934169942677	9	20.0%
custom 5970047654321721218	7	15.6%
custom 5399952619076596235	6	13.3%
custom 5972333199693452259	6	13.3%
custom 5972213288501514320	5	11.1%
custom 5970022399914021879	4	8.89%
custom 5972105055325655452	4	8.89%
custom 5969830251667134066	2	4.44%
custom 5972187647546758298	1	2.22%
custom 5972199639095447821	1	2.22%

Custom emoji. Every row above is a 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 2 of the 3 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 45reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 3 most recent posts we hold, published 6 September 2025 to 1 October 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.

Citation-graph rank

Citation-graph rank — 858,007 of 1,169,250entries 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.

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.

عالم التطبيقات | ALTORKY
@CQ_SO · 5,3302 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.

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

“لــ حمو التركي” (@PS_SPZ), 22 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/PS_SPZ.

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.