Telegram RegisterThe public register of Telegram
Telegram profile photo for ملکه اعظم 👸🏻

Channel

ملکه اعظم 👸🏻

@QueenAazam

On this record: Topic · Observations · Growth · Engagement · What this channel posts · Reactions · Posts · Posts recorded as deleted · Citations · Cite this entry

16,526subscribers

+11,142 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 10,000–31,623.

Register entry

Telegram ID-1003302692819
TypeChannel
Username@QueenAazam
Descriptionاینجا سرزمین ملکه‌هاست 👑 ورود آقایان ممنوع 🚫😌 برای تبلیغ و تبادل: ‎ @AzamQueen ساعت پاسخگویی ۱۵ الی ۲۳ (وی یک کارمند است و هفت صبح به سرکار می‌رود 😭🥺)
CreatedBetween 1 November 2025 and 31 March 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live12 November 2026
Measurements held41
Confirmed unchanged1 time, most recently 12 November 2026
On Telegramt.me/QueenAazam

Topic

Memes & entertainment — 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 11 September 2026 and assigned it the closest of 31 fixed categories, at 61% 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 the other topics.

Observations

These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.

Content that also appears on other registered channels

Posts published here appear in near-verbatim form on 3 other registered channels. The matching is on the text itself, not on Telegram’s forward marker, so it finds a copy whether or not it was labelled as one.

Matching posts — open both and compare (6 of the pairs behind the counts below)
Posted firstThenOverlapGap
@QueenAazam/10860 · this entry7 Nov 2026, 14:40 UTC@BegaByteChannel/165678 Nov 2026, 07:04 UTC0.9916 hours
@QueenAazam/10739 · this entry5 Nov 2026, 05:50 UTC@BegaByteChannel/165477 Nov 2026, 14:08 UTC0.962 days
@QueenAazam/5283 · this entry8 Aug 2026, 12:20 UTC@BegaByteChannel/134748 Aug 2026, 13:34 UTC0.9674 minutes
@QueenAazam/5558 · this entry11 Aug 2026, 16:10 UTC@BegaByteChannel/1390221 Aug 2026, 13:31 UTC0.9610 days
@QueenAazam/10884 · this entry7 Nov 2026, 18:50 UTC@BegaByteChannel/1668411 Nov 2026, 14:03 UTC0.954 days
@QueenAazam/10628 · this entry3 Nov 2026, 08:30 UTC@BegaByteChannel/164765 Nov 2026, 15:32 UTC0.942 days
Channels this entry shares post bodies with, where at least one matching post pair has no forward credit between the two channels, or to a common source, recorded in our data
ChannelMatching postsText overlapTypical gapPublished first
@BegaByteChannel9 (8/8 hand-verifiable sample passed)0.9547 hoursthis entry (9–0)
@HOBBOOT8 (8/8 hand-verifiable sample passed)0.9618 hoursthis entry (7–1)
@sut_tw5 (5/5 hand-verifiable sample passed)0.9524 hours@sut_tw (3–2)

Text overlap is the Jaccard coefficient over the set of distinct three-word phrases in the two bodies: 1.00 is identical wording, and the threshold for counting a pair at all is 0.70. Candidates are generated by simhash LSH (4 x 16-bit bands, exact Hamming <= 3) verified against the bodies with Jaccard over the SET of distinct 3-word shingles. Published first counts which side of each matching pair carries the earlier timestamp — in this corpus, which is the limitation directly below.

What this cannot establish

MEASURED, DOMINANT ERROR SOURCE: a post ingested before 2026-08-06 may have carried a forward header that was not recorded. A 45-pair hand-check against live t.me pages found 14 (31%) where the live page shows a forward header naming the other channel and the database has none, plus 4 more (9%) naming a third party. The text match itself was wrong 0 times out of 45. Read attribution_capture.items_in_trusted_window before treating the unattributed count as a claim.

Telegram lets a channel forward a post with a header naming the source, and we only began reliably recording that header on 2026-08-06. 3 of the 3 matches recorded here fall after that date and carried no header when we read them. The rest predate reliable capture and are not evidence either way.

“Published first” means first in this corpus. We hold 207 comparable posts for this entry, running 7 August 2026 to 11 November 2026. A channel we have read one page deep will look younger than a neighbour we have read in full, and the order would flip with no change in the underlying facts.

The detector’s own notes on this observation, as it recorded them. Names in this_style are fields of the underlying evidence record, which the plain-English paragraphs above read out for this entry.

  • Verbatim republication has three causes and the text separates only two: a clone/mirror, unattributed copy-paste, or BOTH channels copying a common third source that neither attributes. The spread filter (content held by at most 8 channels) reduces the third and does not remove it.
  • 'Earliest' means earliest IN THIS CORPUS. A channel ingested one page deep will look younger than a neighbour ingested in full; corpus_coverage above is there to be checked before the direction is believed.
  • shared_verified_est extrapolates the sampled pass rate over the full narrow match count; sampled/passed are the numbers actually measured.
  • Absence of a forward header is not proof of intent: Telegram lets a channel disable forward attribution, and a credit written in the body is not parsed as attribution here (mention_edge_either_way above is the closest available signal).

Recorded under the keys clone_mutual · clone_source, last confirmed 12 November 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.

Growth

216,6478,324.57 August 2026 — 5,384 subscribers7 August 2026 — 5,384 subscribers8 August 2026 — 5,479 subscribers11 August 2026 — 6,426 subscribers14 August 2026 — 6,485 subscribers17 August 2026 — 6,931 subscribers20 August 2026 — 6,885 subscribers24 August 2026 — 6,787 subscribers27 August 2026 — 6,823 subscribers30 August 2026 — 7,665 subscribers1 September 2026 — 7,965 subscribers5 September 2026 — 9,284 subscribers10 September 2026 — 9,737 subscribers14 September 2026 — 9,629 subscribers18 September 2026 — 10,237 subscribers24 September 2026 — 10,892 subscribers3 October 2026 — 12,400 subscribers8 October 2026 — 12,202 subscribers12 October 2026 — 12,497 subscribers14 October 2026 — 12,455 subscribers15 October 2026 — 12,410 subscribers16 October 2026 — 12,423 subscribers17 October 2026 — 12,382 subscribers18 October 2026 — 12,354 subscribers19 October 2026 — 12,339 subscribers20 October 2026 — 12,324 subscribers21 October 2026 — 12,309 subscribers22 October 2026 — 12,260 subscribers23 October 2026 — 12,966 subscribers24 October 2026 — 13,163 subscribers25 October 2026 — 13,263 subscribers26 October 2026 — 2 subscribers2 November 2026 — 16,647 subscribers3 November 2026 — 16,559 subscribers4 November 2026 — 16,469 subscribers5 November 2026 — 16,408 subscribers6 November 2026 — 16,339 subscribers7 November 2026 — 16,276 subscribers8 November 2026 — 16,182 subscribers10 November 2026 — 16,081 subscribers12 November 2026 — 16,526 subscribers16,5267 August 202612 November 2026
41 measurements spanning 97 days, net +11,142. 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”.
Measurement log — every subscribers count we have recorded, most recent 20 of 41
Measured (UTC)SubscribersChange
12 Nov 2026, 09:4816,526+445
10 Nov 2026, 09:0916,081-101
8 Nov 2026, 19:2116,182-94
7 Nov 2026, 13:1616,276-63
6 Nov 2026, 16:0916,339-69
5 Nov 2026, 19:1016,408-61
4 Nov 2026, 19:5016,469-90
3 Nov 2026, 18:4516,559-88
2 Nov 2026, 21:1016,647+16,645
26 Oct 2026, 19:362-13,261
25 Oct 2026, 22:2613,263+100
24 Oct 2026, 19:3913,163+197
23 Oct 2026, 20:0112,966+706
22 Oct 2026, 19:3012,260-49
21 Oct 2026, 11:5812,309-15
20 Oct 2026, 06:4912,324-15
19 Oct 2026, 08:5512,339-15
18 Oct 2026, 08:3612,354-28
17 Oct 2026, 08:4612,382-41
16 Oct 2026, 06:3512,423first reading

Engagement

410 posts held, back to 7 August 2026 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 31 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
17.1%
avg views ÷ 16,526 subscribers
Avg views / post
2,830
284 posts measured
Reaction rate
6.86%
reactions ÷ views · ER floor
Posts in window
284
of 410 held

ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.

ER is defined industry-wide as (forwards + reactions + comments) ÷ views — note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate. It is computed over the 283 of 284 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 12 November 2026
Posts held410 (7 August 2026 – 12 November 2026)
Views total803,345
Reactions total55,139
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken12 Nov 2026, 18:49 UTC

Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.

Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.

Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.

What this channel posts

Photos
≈3,010
Videos
≈517
Links
≈73

Lifetime counters from Telegram’s own channel header, read 12 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.

Video runtime
36m 08s
Average length
44s

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

68,746 reactions across 409 posts, in 63 distinct kinds. The most used accounts for 28.4% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍19,50828.4%
🤣15,76122.9%
❤9,16213.3%
💔7,04610.2%
😁3,1764.62%
👏2,2423.26%
🥰1,9872.89%
😐1,2861.87%
😭9971.45%
👎8471.23%
😢6921.01%
🤬6921.01%
🤝6430.935%
😍6180.899%
👌6110.889%
🖕4560.663%
❤‍🔥3400.495%
🤡2910.423%
🤮2870.417%
💩2760.401%
43 further kinds1,8282.66%

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 409 of the 410 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 68,746 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 410 most recent posts we hold, published 7 August 2026 to 12 November 2026, 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

Telegram’s own ‘edited’ marker: 0 of 284 posts held from the last 30 days (0%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).

12 Nov 2026, 18:44 UTC307 views24 reactionsread 12 November 2026

اگه پسر بودم بهتون نشون میدادم چطور باید یکیو دوست داشت. ×𝗡× @QueenAazam

❤20👍3🐳1

12 Nov 2026, 18:30 UTC729 views36 reactionsread 12 November 2026
Photo

در ستایش نور: °Mɪʟᴀᴅ° @QueenAazam

❤31🔥5

12 Nov 2026, 18:26 UTC852 views21 reactionsread 12 November 2026
Video

زندگی انقدر طولانی نیست... که برای شاد بودن... منتظر تموم شدن سختی ها باشیم!🥰 °ســــــــــایه° @QueenAazam

❤18🌚2👍1

12 Nov 2026, 18:19 UTC≈1,060 views72 reactionsread 12 November 2026

یادم باشه دوتا سیمکارت جدید بخرم تو ثبت نام خوابگاه و دانشگاه به جای شماره مامان بابام شماره های جدید خودمو بدم. °kiana° @QueenAazam

👍45😁14❤4😭4😐3🌚1🤣1

12 Nov 2026, 18:12 UTC≈1,190 views31 reactionsread 12 November 2026
Video

°طبخة ° @QueenAazam

🔥22❤5🤮2👌1😭1

12 Nov 2026, 18:05 UTC≈1,280 views76 reactionsread 12 November 2026

? سالهاست رانندگی میکنم و در حد خودم راننده بدی نیستم، يه روز تو جاده خسته بودم به همسرم گفتم اون پشت فرمون بشیه، صحنه‌ای که اگه ۱۰۰۰ بار هم تکرار میشد من قطعا ۱۰۰۰ بار شاخ به شاخ میزدم، ایشون با معکوس کشیدن طوری جمع کرد که هنوزم باورم نمیشه. همه‌ی ما فارق از جنسیتمون تصادف کردیم، ? همه‌ی ما زمانی که تازه‌کار بودیم مهارت کافی نداشتیم، فقط چون فکر می‌کنیم کسی اون روزهای ما رو ندیده میتونیم با غرور دیگران رو مسخره کنیم…

❤60👌11👍4🌚1

12 Nov 2026, 17:58 UTC≈1,370 views7 reactionsread 12 November 2026
Video

Yo mirando la habitación que limpié. °‏ًً° @QueenAazam

❤4🌚1🤣1🤯1

12 Nov 2026, 17:26 UTC≈1,760 views120 reactionsread 12 November 2026

ببینید دوستان، اینکه یکی سینگله، به این معنی نیست که بدبخته و درمونده‌ست. اتفاقا کسی درمونده‌ست که به‌خاطر ناامنی‌ها و نداشتن اعتمادبه‌نفس توی یه رابطه‌‌ی سمی می‌مونه. °سنیور° @QueenAazam

👍101❤11👌3💔3💘2

12 Nov 2026, 17:19 UTC≈1,850 views106 reactionsread 12 November 2026

عزیزم امیدوارم کارما یجوری کونتو بگاد که دنبال یه کون جدید بگردی. °آیدام° @QueenAazam

👍87😁10❤4👏2🌚1💔1🤮1

12 Nov 2026, 17:12 UTC≈1,910 views184 reactionsread 12 November 2026

به نظرم این‌ که یکی بخواد باهات آشنا شه چون صرفا فکر میکنه "خوشگلی" خیلی تحقیرآمیز محسوب میشه. °Su° @QueenAazam

👍158❤10🤔6👎5😁2😐2🍌1

12 Nov 2026, 16:51 UTC≈2,120 views121 reactionsread 12 November 2026

بپذیر که یه رهگذر بود. °A° @QueenAazam

💔84🕊17👍14❤4👎2

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

Posts recorded as deleted after publishing

We recorded 3 posts on @QueenAazam as deleted — posts this register held that were missing from the channel’s public page on two separate reads, taken from different network addresses at least an hour apart.

A deletion is not wrongdoing. This register can see that a post it held is no longer on the channel’s public page, and when — not why. Expired ad placements, reposts, rotating links and corrections all look the same. This is a count of recorded detections, not an exact total: it misses deletions we could not see, because only a post we held and later re-read inside the page can be seen to go, and it may include a small number of wrong records. How this is measured.

First seen missing
8 August 2026
Most recent seen missing
5 November 2026
Median time before seen missing
12 hours
Seen missing in the last 30 days
2

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

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

Named by 3 registered channels — 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.

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

“ملکه اعظم 👸🏻” (@QueenAazam), 16,526 subscribers as measured 12 November 2026. Telegram Register, tgregister.com/channel/QueenAazam.

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.