Telegram RegisterThe public register of Telegram
Telegram profile photo for متجر جوي

Channel

متجر جوي

@H39nn

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

12subscribers

+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-1002203273494
TypeChannel
Username@H39nn
CreatedBetween 1 June 2024 and 10 July 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded12 August 2026
Last confirmed live30 August 2026
Measurements held2
On Telegramt.me/H39nn

Growth

127 August 2026 — 12 subscribers12 August 2026 — 12 subscribers7 August 202612 August 2026
2 measurements spanning 5 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 11–13 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Aug 2026, 05:1512no change
7 Aug 2026, 14:1512first reading

Engagement

14 posts held, back to 10 July 2024the 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 14 posts for this entry, the most recent from 5 February 2025. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
10
Videos
2
Links
1

Lifetime counters from Telegram’s own channel header, read 12 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
8m 39s
Average length
4m 20s

Measured directly from 2 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

41 reactions across 6 posts, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 537290449559434848341100.0%

Custom emoji. One 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 count beside it isTelegram’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 6 of the 14 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 41reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 14 most recent posts we hold, published 10 July 2024 to 5 February 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

5 Feb 2025, 19:27 UTC23 viewsread 12 August 2026
Forwarded from @FJ377s

بما انو تعبان و مشتاقلكم كلت اسولف وياكم @E2nnBoT قناه : @n5ssn

18 Jan 2025, 04:48 UTC130 viewsread 12 August 2026

اقوى سوبر للقنوات و التمويل صاعد حالياً 🍓💙. https://t.me/+GL0C0AveZx04ZDZk متتخيلون شكد اعضائه مرتبين و كلش هادئ و مابي مشاكل 🍓❤️. دز طلب نقبلك 🍓💙.

6 Dec 2024, 11:04 UTC274 viewsread 12 August 2026
Video

تصوير جديد للحساب . تواصل @R37nn

22 Oct 2024, 17:33 UTC535 viewsread 12 August 2026
Video

تفاصيل الحساب 🔥 شعبيه الحساب : 3.5M بداخله هالكوبتر و 10 سيارات ✅✅ 20 سلاح يتطور منهم - 14 كل مسج و واحد لفل 3 بي اكثر من 55 مثك ❤️✅ بي 2 لبسات الأصفر 💛✅ بي اكثر من 200 لبس وردي 💘✅ بي اكثر من 25 مضله 💃 بي امفور ماكس الصندوق 💜✅ بي لامبرجيني ابيضّ 🤍✅ سعر الحساب : 🇮🇶 اقبل زينكاش او اسيا او وجه ل وجه داخل النجف او بغداد شراي دز خاص : @R37nn

18 Oct 2024, 15:15 UTC387 viewsread 12 August 2026
Photo

القوي 💪💀 عدد :2600 لايكات : 4ك مُحتوى : بناتي سعر : 6 زينكاش او اسيا تواصل : @R37nn

10 Jul 2024, 09:04 UTC503 views6 reactionsread 12 August 2026
Photo

القوي 💪🤍 قناه تلي كُلها حقيقي عدد : 2.1K تفاعل يومي : +300 رابط : @R37uu سعر : نباعت تواصل : @نباعت

custom 53729044955943484836

10 Jul 2024, 09:01 UTC418 views9 reactionsread 12 August 2026
Photo

القوي 💪💀 حساب مُتفاعل عام و ستوري عدد : 21.8K ستوري : +1K سعر؟ : 55 و بي مجال تواصل : @نباع

custom 53729044955943484839

10 Jul 2024, 08:58 UTC294 views5 reactionsread 12 August 2026
Photo

القوي 💪 🤍 المستوى : 46 قريب جداً على 47 الروم : 10 مايك مُتفاعل جداً سعر : 150 و بي مجال للشراي تواصل : @R37nn

custom 53729044955943484835

10 Jul 2024, 08:53 UTC293 views7 reactionsread 12 August 2026
Photo

القوي 💪💀 عدد : 10.4K لايكات : 122K مُحتوى : ببجي سعر : 30 زينكاش او اسيا تواصل : @R37nn

custom 53729044955943484837

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

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.

Mentions

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.

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

“متجر جوي” (@H39nn), 12 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/H39nn.

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.