Telegram RegisterThe public register of Telegram
Telegram profile photo for موج؛

Channel

موج؛

@mojnot

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

29,807subscribers

-24,050 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-1002425195957
TypeChannel
Username@mojnot
Descriptionاینجا به حرفام میرسی. 🌊 @mojnotAd
CreatedBetween 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live8 October 2026
Measurements held37
Confirmed unchanged1 time, most recently 8 October 2026
On Telegramt.me/mojnot

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 9 September 2026 and assigned it the closest of 31 fixed categories, at 62% 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

29,80753,85741,8327 August 2026 — 53,857 subscribers7 August 2026 — 53,857 subscribers8 August 2026 — 53,576 subscribers9 August 2026 — 53,280 subscribers10 August 2026 — 53,036 subscribers11 August 2026 — 52,784 subscribers12 August 2026 — 52,507 subscribers13 August 2026 — 52,332 subscribers14 August 2026 — 52,070 subscribers16 August 2026 — 51,841 subscribers17 August 2026 — 51,598 subscribers18 August 2026 — 51,293 subscribers19 August 2026 — 51,101 subscribers20 August 2026 — 50,963 subscribers21 August 2026 — 50,773 subscribers22 August 2026 — 50,499 subscribers24 August 2026 — 50,302 subscribers25 August 2026 — 50,170 subscribers26 August 2026 — 50,079 subscribers27 August 2026 — 49,995 subscribers28 August 2026 — 49,883 subscribers29 August 2026 — 49,708 subscribers30 August 2026 — 49,304 subscribers31 August 2026 — 48,737 subscribers1 September 2026 — 48,391 subscribers2 September 2026 — 47,890 subscribers3 September 2026 — 47,131 subscribers4 September 2026 — 45,640 subscribers8 September 2026 — 43,197 subscribers11 September 2026 — 41,067 subscribers13 September 2026 — 39,741 subscribers14 September 2026 — 39,041 subscribers16 September 2026 — 37,973 subscribers18 September 2026 — 36,329 subscribers24 September 2026 — 32,725 subscribers3 October 2026 — 30,793 subscribers8 October 2026 — 29,807 subscribers7 August 20268 October 2026
37 measurements spanning 62 days, net -24,050. 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 26,200–57,465 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 37
Measured (UTC)SubscribersChange
8 Oct 2026, 06:1829,807-986
3 Oct 2026, 14:4030,793-1,932
24 Sept 2026, 21:4232,725-3,604
18 Sept 2026, 16:1836,329-1,644
16 Sept 2026, 06:5737,973-1,068
14 Sept 2026, 15:3839,041-700
13 Sept 2026, 04:3839,741-1,326
11 Sept 2026, 05:1641,067-2,130
8 Sept 2026, 05:4143,197-2,443
4 Sept 2026, 23:1545,640-1,491
3 Sept 2026, 06:4947,131-759
2 Sept 2026, 04:5247,890-501
1 Sept 2026, 03:1548,391-346
31 Aug 2026, 06:0248,737-567
30 Aug 2026, 08:0849,304-404
29 Aug 2026, 09:4249,708-175
28 Aug 2026, 10:2549,883-112
27 Aug 2026, 10:1149,995-84
26 Aug 2026, 13:1650,079-91
25 Aug 2026, 16:4450,170first reading

Engagement

366 posts held, back to 2 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 128 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
4.35%
avg views ÷ 29,807 subscribers
Avg views / post
1,300
243 posts measured
Reaction rate
0.881%
reactions ÷ views · ER floor
Posts in window
243
of 366 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 209 of 243 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 8 October 2026
Posts held366 (2 August 2026 – 8 October 2026)
Views total314,865
Reactions total2,345
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken8 Oct 2026, 09:53 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
79
Videos
6
Links
11

Lifetime counters from Telegram’s own channel header, read 8 October 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
49s
Average length
10s

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

2,345 reactions across 209 posts, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤2,345100.0%

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 209 of the 366 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 2,345 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 366 most recent posts we hold, published 2 August 2026 to 8 October 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

8 Oct 2026, 09:40 UTC63 viewsread 8 October 2026

نیاز به بغل شدن توسط اون دختره دارم.

8 Oct 2026, 08:30 UTC238 views4 reactionsread 8 October 2026

ولی من دوست دارم جای کبودیای تو همیشه روی بدنم باشه.

❤4

8 Oct 2026, 07:12 UTC343 views3 reactionsread 8 October 2026

امروز October 8، روز جهانیِ برونگرا هاست.

❤3

8 Oct 2026, 00:00 UTC730 views11 reactionsread 8 October 2026

خطرناک‌ترین نوعِ خشم، خشمیه که تو دلِ یه آدم مهربون جمع می‌شه.

❤11

7 Oct 2026, 22:10 UTC661 views8 reactionsread 8 October 2026

خدا بهت لب داده تا گردن و لبای منو باهاشون ببوسی پسره.

❤8

7 Oct 2026, 21:10 UTC741 views12 reactionsread 8 October 2026

شب شده پر ستاره، اورثینک میگاد دوباره.

❤12

7 Oct 2026, 19:05 UTC891 views35 reactionsread 8 October 2026

معنی عشق رو نفهمیده بودم تا زمانی که یه دختر به یه اعدامی بله گفت.

❤35

7 Oct 2026, 17:31 UTC970 views15 reactionsread 8 October 2026

دخترای هات یک گردنبند مورد علاقه دارن که همیشه گردنشونه.

❤15

7 Oct 2026, 16:34 UTC986 views10 reactionsread 8 October 2026

وانمود میکنم از همچی رد شدم ولی ردش روی روح و روانم مونده.

❤10

7 Oct 2026, 15:33 UTC989 views6 reactionsread 8 October 2026

منو شاید بتونی فراموش کنی ولی چشامو چی؟

❤6

7 Oct 2026, 14:42 UTC≈1,020 views8 reactionsread 8 October 2026

حداقل دلی که خودت توش بودی رو نمیشکوندی.

❤8

7 Oct 2026, 13:34 UTC≈1,030 views8 reactionsread 8 October 2026

از لحاظ روحی نیاز دارم تو بغلت باشم و قربون صدقم بری.

❤8

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

Republished by

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

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

“موج؛” (@mojnot), 29,807 subscribers as measured 8 October 2026. Telegram Register, tgregister.com/channel/mojnot.

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.