Telegram RegisterThe public register of Telegram

Channel

Art Impact | Genshin Impact | Honkai Star Rail

@GIHSRARTs

On this record: Topic · Observations · Also posting the same content · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry

1,528subscribers

-4 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1001699954720
TypeChannel
Username@GIHSRARTs
CreatedBetween 1 December 2021 and 31 March 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live10 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 10 August 2026
On Telegramt.me/GIHSRARTs

Topic

Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 11 August 2026 and assigned it the closest of 31 fixed categories, at 60% 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.

Observations

These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.

Content that also appears on other registered channels

Posts published here appear word for word on 1 other registered channel. The matching is on the text itself, not on Telegram’s forward marker, so it finds a copy whether or not it was labelled as one.

Matching posts — open both and compare (5 of the pairs behind the counts below)
Posted firstThenOverlapGap
@GIHSRARTs/13757 · this entry31 Mar 2025, 19:06 UTC@mikasaeditor/495431 Mar 2025, 19:06 UTC1.00under a minute
@mikasaeditor/49604 Apr 2025, 19:04 UTC@GIHSRARTs/13763 · this entry4 Apr 2025, 19:04 UTC1.00under a minute
@GIHSRARTs/13768 · this entry5 Apr 2025, 12:04 UTC@mikasaeditor/49655 Apr 2025, 12:06 UTC1.002 minutes
@GIHSRARTs/13772 · this entry11 Apr 2025, 15:07 UTC@mikasaeditor/496911 Apr 2025, 15:07 UTC1.00under a minute
@mikasaeditor/497013 May 2025, 12:00 UTC@GIHSRARTs/13773 · this entry13 May 2025, 12:00 UTC1.00under a minute
Every channel this entry shares post bodies with
ChannelMatching postsText overlapTypical gapPublished first
@mikasaeditor6 (5/6 hand-verifiable sample passed)1.00under a minuteeven

Text overlap is the Jaccard coefficient over the set of distinct three-word phrases in the two bodies: 1.00 is identical wording, and the threshold for counting a pair at all is 0.70. Candidates are generated by simhash LSH (4 x 16-bit bands, exact Hamming <= 3) verified against the bodies with Jaccard over the SET of distinct 3-word shingles. Published first counts which side of each matching pair carries the earlier timestamp — in this corpus, which is the limitation directly below.

What this cannot establish

MEASURED, DOMINANT ERROR SOURCE: a post ingested before 2026-08-06 may have carried a forward header that was not recorded. A 45-pair hand-check against live t.me pages found 14 (31%) where the live page shows a forward header naming the other channel and the database has none, plus 4 more (9%) naming a third party. The text match itself was wrong 0 times out of 45. Read attribution_capture.items_in_trusted_window before treating the unattributed count as a claim.

Telegram lets a channel forward a post with a header naming the source, and we only began reliably recording that header on 2026-08-06. None of the 3 matches recorded here fall after that date, so for this entry we cannot say whether any of them carried a credit. The duplication is measured; the absence of attribution is not.

“Published first” means first in this corpus. We hold 6 comparable posts for this entry, running 30 March 2025 to 13 May 2025. A channel we have read one page deep will look younger than a neighbour we have read in full, and the order would flip with no change in the underlying facts.

The detector’s own notes on this observation, as it recorded them. Names in this_style are fields of the underlying evidence record, which the plain-English paragraphs above read out for this entry.

  • Verbatim republication has three causes and the text separates only two: a clone/mirror, unattributed copy-paste, or BOTH channels copying a common third source that neither attributes. The spread filter (content held by at most 8 channels) reduces the third and does not remove it.
  • 'Earliest' means earliest IN THIS CORPUS. A channel ingested one page deep will look younger than a neighbour ingested in full; corpus_coverage above is there to be checked before the direction is believed.
  • shared_verified_est extrapolates the sampled pass rate over the full narrow match count; sampled/passed are the numbers actually measured.
  • Absence of a forward header is not proof of intent: Telegram lets a channel disable forward attribution, and a credit written in the body is not parsed as attribution here (mention_edge_either_way above is the closest available signal).

Across the whole group of 2, the earliest publisher we hold is @mikasaeditor. That is a statement about our reading window, not a claim of authorship.

Recorded under the key clone_mutual, last confirmed 8 August 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.

Also posting the same content

This channel’s posts match, word for word or near enough, posts on 1 other registered channel, found by comparing text fingerprints across every channel on the register. That matching has been checked by hand against the live Telegram pages and found reliable — 0 wrong of 45 pairs re-read.

Which channel, if either, published first is deliberately not shown. The same hand-check found that reading wrong 18 of 45 times — 60%, no better than a coin flip — because it depends on how deep our own crawl happened to reach into each channel’s history, not on when the content was actually first posted. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Word-for-word matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.

Growth

1,5281,5321,5307 August 2026 — 1,532 subscribers7 August 2026 — 1,532 subscribers10 August 2026 — 1,528 subscribers7 August 202610 August 2026
3 measurements spanning 4 days, net -4. 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 1,527–1,533 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
10 Aug 2026, 23:231,528-4
7 Aug 2026, 10:321,532no change
7 Aug 2026, 10:201,532first reading

Engagement

18 posts held, back to 30 March 2025the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 2 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 13 May 2025. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
17s
Average length
17s

Measured directly from 1 video 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

5 reactions across 2 posts, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
😭5100.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 3 of the 18 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 5reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 18 most recent posts we hold, published 30 March 2025 to 13 May 2025, 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

13 May 2025, 12:00 UTC795 views4 reactionsread 7 August 2026
Photo

Добрый день, подпищеки! Нашел Для вас приятные каналы с эстетиками, рекомендую ознакомиться🥰🙏 Gothic core🕷 [Мрачный, готический] Nature core🌱 [Природа] Emo core☠️ [Эмо 2007] Metal core🕷 [Еее роцк] Dream core🌿 [Приснилось] Alt core👽 [Альтушки] Satan core👹 [666] Angel core😇 [Рай на земле] Vampire core🩸 [кровосиси] Japan coreя🇯🇵 [Азия] Slavic core🇷🇺 [НАШ вайбик] ПРАВОСЛАВНЫЙ core☦️ [🙏🙏🙏] Winter core❄️ [Зимний вайбик]

😭4

11 Apr 2025, 15:07 UTC708 viewsread 7 August 2026

Девочки, для каждого имени сделали каналы с гороскопами и знаками судьбы❤️ Родная, ищи себя: знак Аделине l гороскоп Аделине знак Алёне l гороскоп Алёне знак Алине l гороскоп Алине знак Алисе l гороскоп Алисе знак Амине l гороскоп Амине знак Ангелине l гороскоп Ангелине знак Ане l гороскоп Ане знак Арине l гороскоп Арине знак Вале l гороскоп Вале знак Василисе l гороскоп Василисе знак Веронике l гороскоп Веронике з

11 Apr 2025, 13:14 UTC562 viewsread 7 August 2026

Неадекватные фанаты лезут к ПАШЕ ТЕХНИКУ на похоронах 👆🏻

11 Apr 2025, 13:00 UTC557 viewsread 7 August 2026
Photo

‼️ Начались похороны Паши ТЕХНИКА Прямая трансляция в Топор+

9 Apr 2025, 12:04 UTC514 viewsread 7 August 2026
Photo

Кидаем ссылки на лучших ботов из C Ai 🤒 Чекай че уже выложили: https://t.me/+rGyE77TYI5NiMzM6

5 Apr 2025, 12:04 UTC443 views1 reactionsread 7 August 2026
Photo

Он(а) 10/10, но он(а) не подписан(а) на эти каналы...🥺👇 👨‍🦰Он 10/10, но | Она 10/10, но👩‍🦰

😭1

5 Apr 2025, 12:04 UTC474 viewsread 7 August 2026

👩‍🦰Для НЕГО: Секреты, женские штучки, которые ТЫ никогда не поймешь! ➡️ [Она 10/10] 👨‍🦰Для НЕЁ: Как выжить в мире мужской логики?!➡️ [Он 10/10]

5 Apr 2025, 10:08 UTC421 viewsread 7 August 2026

Кадры с последних минут жизни Паши Техника ☝🏼😨

5 Apr 2025, 09:39 UTC408 viewsread 7 August 2026
Photo

Жесткие кадры с последних минут жизни Паши Техника Фото и подробности в Топоре+

4 Apr 2025, 20:20 UTC351 viewsread 7 August 2026
Photo

Паша Техник умер. За его жизнь боролись тайские врачи. Подробности в Топоре+

4 Apr 2025, 19:04 UTC318 viewsread 7 August 2026

Изучаешь языки? Для тебя создали каналы каналы с подробным объяснением всех тем каждого языка, welcome 👇 Английский Корейский Немецкий Французский Русский Китайский Японский Испанский Украинский Татарский Итальянский Белорусский Латынь Турецкий Армянский Арабский Польский Остальные языки тут

4 Apr 2025, 15:04 UTC272 viewsread 7 August 2026

💬 Все ржачные комменты с тик тока и инсты собрали в одном канале 👀 Ссылка на канал: t.me/+GqOjFK49W9Q4ZTky

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

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.

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

“Art Impact | Genshin Impact | Honkai Star Rail” (@GIHSRARTs), 1,528 subscribers as measured 10 August 2026. Telegram Register, tgregister.com/channel/GIHSRARTs.

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.