Channel
پروژه تاریخ شفاهی ایران هاروارد (IRANIAN ORAL HISTORY PROJECT)
@IOHP3
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
13,594subscribers
+22 since we began measuring on 7 September 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
Register entry
| Telegram ID | -1001222146911 |
|---|---|
| Type | Channel |
| Username | @IOHP3 |
| Created | 23 June 2018 — measured — cross-checked against a third-party dataset (TGDataset) |
| First recorded | 7 September 2026 |
| Last confirmed live | 26 October 2026 |
| Measurements held | 21 |
| Confirmed unchanged | 1 time, most recently 26 October 2026 |
| On Telegram | t.me/IOHP3 |
Topic
Other / unclassifiable — 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 27 September 2026 and assigned it the closest of 31 fixed categories, at 77% 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
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 26 Oct 2026, 02:10 | 13,594 | -6 |
| 24 Oct 2026, 01:06 | 13,600 | +2 |
| 23 Oct 2026, 02:46 | 13,598 | +1 |
| 22 Oct 2026, 00:45 | 13,597 | +4 |
| 20 Oct 2026, 17:09 | 13,593 | +5 |
| 19 Oct 2026, 18:00 | 13,588 | -1 |
| 17 Oct 2026, 22:00 | 13,589 | +6 |
| 16 Oct 2026, 21:55 | 13,583 | +3 |
| 15 Oct 2026, 18:31 | 13,580 | +7 |
| 14 Oct 2026, 15:07 | 13,573 | +1 |
| 13 Oct 2026, 07:15 | 13,572 | +3 |
| 9 Oct 2026, 03:37 | 13,569 | +8 |
| 4 Oct 2026, 18:37 | 13,561 | -2 |
| 27 Sept 2026, 00:55 | 13,563 | -4 |
| 17 Sept 2026, 12:41 | 13,567 | -2 |
| 15 Sept 2026, 14:40 | 13,569 | +4 |
| 14 Sept 2026, 01:38 | 13,565 | -4 |
| 12 Sept 2026, 05:20 | 13,569 | -1 |
| 9 Sept 2026, 21:57 | 13,570 | -2 |
| 7 Sept 2026, 19:40 | 13,572 | first reading |
Engagement
Posts not read yet. This entry is on the register from its profile alone; the post reader has not reached it. Engagement figures appear here once posts have actually been measured — we do not publish a rate before we have the readings behind 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.
@Alihatami_advisor · 28,083
Telegram ranks this channel #31 of 57 here — alongside 56 others — read 9 September 2026
@KetabJibiPodcast · 31,006
Telegram ranks this channel #38 of 71 here — alongside 70 others — read 7 September 2026
@ir24onlinenews · 43,602
Telegram ranks this channel #61 of 80 here — alongside 79 others — read 29 September 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 26 October 2026 — this entry's latest reading, not the date you are reading this.
“پروژه تاریخ شفاهی ایران هاروارد (IRANIAN ORAL HISTORY PROJECT)” (@IOHP3), 13,594 subscribers as measured 26 October 2026. Telegram Register, tgregister.com/channel/IOHP3.
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.