Telegram RegisterThe public register of Telegram
Telegram profile photo for ๐Ÿ‘‘ ํ…”๋ ˆ๊ทธ๋žจ ํ™๋ณด ๋Œ€ํ†ต๋ น๐Ÿ‘‘

Supergroup

๐Ÿ‘‘ ํ…”๋ ˆ๊ทธ๋žจ ํ™๋ณด ๋Œ€ํ†ต๋ น๐Ÿ‘‘

@Public_Relations_President

On this record: Growth ยท Engagement ยท Citations ยท Cite this entry

4,472members

+432 since we began measuring on 7 August 2026

14 online right now

Risers and fallers across the register ยท movement among entries of 3,162โ€“10,000.

Register entry

Telegram ID-1002088737015
TypeSupergroup
Username@Public_Relations_President
CreatedBetween 1 November 2023 and 31 May 2024 โ€” estimated from Telegramโ€™s id allocation, not measured. How this range is calculated.
First recorded3 September 2026
Last confirmed live9 September 2026
Measurements held12
Confirmed unchanged1 time, most recently 9 September 2026
On Telegramt.me/Public_Relations_President

Growth

4,0404,4764,2587 August 2026 โ€” 4,040 members8 August 2026 โ€” 4,081 members11 August 2026 โ€” 4,156 members15 August 2026 โ€” 4,166 members18 August 2026 โ€” 4,176 members21 August 2026 โ€” 4,225 members25 August 2026 โ€” 4,257 members28 August 2026 โ€” 4,370 members31 August 2026 โ€” 4,451 members3 September 2026 โ€” 4,451 members4 September 2026 โ€” 4,476 members9 September 2026 โ€” 4,472 members4,4727 August 20269 September 2026
12 measurements spanning 33 days, net +432. 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 3,975โ€“4,541 and does not start at zero.
Measurement log โ€” every members count we have recorded
Measured (UTC)MembersChange
9 Sept 2026, 09:404,472-4
4 Sept 2026, 01:414,476+25
3 Sept 2026, 20:104,451no change
31 Aug 2026, 12:454,451+81
28 Aug 2026, 09:344,370+113
25 Aug 2026, 01:484,257+32
21 Aug 2026, 08:134,225+49
18 Aug 2026, 12:064,176+10
15 Aug 2026, 05:054,166+10
11 Aug 2026, 11:564,156+75
8 Aug 2026, 04:584,081+41
7 Aug 2026, 18:024,040first 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.

Mentions

Named by 1 registered channel โ€” 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.

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 9 September 2026 โ€” this entry's latest reading, not the date you are reading this.

โ€œ๐Ÿ‘‘ ํ…”๋ ˆ๊ทธ๋žจ ํ™๋ณด ๋Œ€ํ†ต๋ น๐Ÿ‘‘โ€ (@Public_Relations_President), 4,472 members as measured 9 September 2026. Telegram Register, tgregister.com/channel/Public_Relations_President.

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.