Telegram RegisterThe public register of Telegram
Telegram profile photo for aishigara

Channel

aishigara

@aishigarasc

On this record: Growth · Engagement · Posts · Citations · Cite this entry

114subscribers

-2 since we began measuring on 13 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1002411126972
TypeChannel
Username@aishigarasc
CreatedBetween 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded13 August 2026
Last confirmed live6 September 2026
Measurements held5
Confirmed unchanged1 time, most recently 6 September 2026
On Telegramt.me/aishigarasc

Growth

11411611513 August 2026 — 116 subscribers13 August 2026 — 116 subscribers21 August 2026 — 114 subscribers29 August 2026 — 116 subscribers6 September 2026 — 114 subscribers13 August 20266 September 2026
5 measurements spanning 24 days, net -2. 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 114–116 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
6 Sept 2026, 05:19114-2
29 Aug 2026, 08:47116+2
21 Aug 2026, 08:28114-2
13 Aug 2026, 13:00116no change
13 Aug 2026, 12:48116first reading

Engagement

20 posts held, back to 25 October 2025the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 page of 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 20 posts for this entry, the most recent from 28 July 2026. An engagement rate over an empty window would be a number about nothing.

Recent posts

27 Jul 2026, 12:55 UTC82 viewsread 13 August 2026

дорогие друзья, я потерял доступ к своему аккаунту и всем тгк можете отписываться от всех моих каналов, я больше не буду их вести. теперь все будет в одном канале ссылка на новый тгк https://t.me/imaishigara https://t.me/imaishigara https://t.me/imaishigara

24 Jul 2026, 05:32 UTC117 viewsread 13 August 2026
Photo

aishigara, фертиван*31 – Goodbye СЛУШАТЬ НА ВСЕХ ПЛОЩАДКАХ

20 Jul 2026, 11:16 UTC208 viewsread 13 August 2026

первый трек после армейки буду очень благодарен вашему активу под ним 🤍 с первого вдоха новой истории

20 Jul 2026, 11:12 UTC≈1,870 viewsread 13 August 2026
Photo

aishigara – Fragrance prod. by coralean mix. by aishigara LISTEN ON SOUNDCLOUD

15 Jul 2026, 09:51 UTC195 viewsread 13 August 2026

гудбай в следующую пятницу на всех площадках, кликайте пресейв https://band.link/Y3rK4

18 Jun 2026, 07:43 UTC453 viewsread 13 August 2026
Photo

ахуеть лям на ск огромное спасибо всем, кто слушает, поддерживает и верит в меня 🩶 любовь. через две недели я возвращаюсь домой, и поверьте, все самое интересное только впереди.

1 May 2026, 12:12 UTC365 viewsread 13 August 2026
Forwarded from @ssgaslinePhoto

EP gas - NOISE> prod. hidrethic, lostupren, wav62, mlrs, im1ky, k4neswagga mix. gas feat - миксидин, aishigara LISTEN IN SOUNDCLOUD

15 Apr 2026, 08:16 UTC≈2,700 viewsread 13 August 2026
Photo

aishigara, gas – Gun or Kiss prod. by im1ky, k4neswagga mix. by gas LISTEN ON SOUNDCLOUD

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

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 2 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.

Named by

Channels on the register whose posts name this channel's handle.

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

“aishigara” (@aishigarasc), 114 subscribers as measured 6 September 2026. Telegram Register, tgregister.com/channel/aishigarasc.

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.