Telegram RegisterThe public register of Telegram
Telegram profile photo for Listening - Awasir OET

Channel

Listening - Awasir OET

@OET_Awaser

On this record: Growth · Engagement · What this channel posts · Posts · Citations · Telegram's recommendations · Cite this entry

17,631subscribers

+21 since we began measuring on 25 August 2026

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

Register entry

Telegram ID-1001852000147
TypeChannel
Username@OET_Awaser
DescriptionWelcome! Prepare for the OET Listening sub-test with tips, practice, and expert guidance.
CreatedBetween 1 October 2022 and 5 November 2022— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded25 August 2026
Last confirmed live28 August 2026
Measurements held6
Confirmed unchanged1 time, most recently 28 August 2026
On Telegramt.me/OET_Awaser

Growth

17,61017,63117,620.525 August 2026 — 17,610 subscribers25 August 2026 — 17,610 subscribers25 August 2026 — 17,612 subscribers26 August 2026 — 17,620 subscribers27 August 2026 — 17,624 subscribers28 August 2026 — 17,631 subscribers25 August 202628 August 2026
6 measurements spanning 3 days, net +21. 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 17,607–17,634 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
28 Aug 2026, 15:2417,631+7
27 Aug 2026, 16:0817,624+4
26 Aug 2026, 19:3817,620+8
25 Aug 2026, 19:0717,612+2
25 Aug 2026, 16:0017,610no change
25 Aug 2026, 15:4517,610first reading

Engagement

18 posts held, back to 5 November 2022 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 7 pagesof 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 18 posts for this entry, the most recent from 27 October 2023. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Videos
21
Links
23

Lifetime counters from Telegram’s own channel header, read 28 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.

Recent posts

5 Nov 2022, 18:02 UTC≈74,300 viewsread 28 August 2026

📌 0- Overview : https://t.me/OETAwasir 📌 1- Writing : https://t.me/OETAwasir2 📌2- Speaking : https://t.me/OETAwaser3 📌 2. Listening : https://t.me/+5-pTsT2Emg9iMmQ0 📌 4- Reading : https://t.me/+8aSVhlB_Tos4M2M0 Good luck 🤞

5 Nov 2022, 18:01 UTC≈51,600 viewsread 28 August 2026

———————————————————————————-

5 Nov 2022, 02:31 UTC≈48,800 viewsread 28 August 2026

- مهم جدا المرور على الكلمات دي لانها بتكرر كتير في الامتحانات - اثناء المرور عليها انتبه للنطق الصحيح للكلمات واتاكد من ال spelling

5 Nov 2022, 02:29 UTC≈45,400 viewsread 28 August 2026

———————————————————————————-

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

Mentions

Names

Channels on the register whose handles appear in this channel's posts.

Speaking - Awasir OET
@OETAwaser3 · 13,4321 postAwasir OET - General
@OETAwasir · 19,0861 postWriting - Awasir OET
@OETAwasir2 · 15,2931 post

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.

Appears in Telegram’s recommendations for other channels

The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.

مكتبة طب الأسنان
@LibraryEDent · 54,516
Telegram ranks this channel #24 of 65 here — alongside 64 others — read 28 August 2026
تعلم حديث
@Talam_Hadith · 50,189
Telegram ranks this channel #43 of 84 here — alongside 83 others — read 25 August 2026
NBME CMS STEP 2 CK | USMLE
@USMLENBME2CK · 74,661
Telegram ranks this channel #52 of 69 here — alongside 68 others — read 26 August 2026

This channel appears in 3 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.

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

“Listening - Awasir OET” (@OET_Awaser), 17,631 subscribers as measured 28 August 2026. Telegram Register, tgregister.com/channel/OET_Awaser.

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.