Telegram RegisterThe public register of Telegram
Telegram profile photo for SHIFFY - YCHs, Commissions & Updates

Channel

SHIFFY - YCHs, Commissions & Updates

@SHIFFYbah

On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry

13subscribers

+0 since we began measuring on 10 August 2026

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

Register entry

Telegram ID-1002472534922
TypeChannel
Username@SHIFFYbah
DescriptionКанал Шиффи, о обновнениях и комишках
Created12 March 2025measured — dated from the channel’s first post
First recorded12 August 2026
Last confirmed live17 August 2026
Measurements held2
On Telegramt.me/SHIFFYbah

Growth

1310 Aug 2026, 18:49 — 13 subscribers12 Aug 2026, 04:02 — 13 subscribers10 Aug 2026, 18:4912 Aug 2026, 04:02
2 measurements spanning 1 day. 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 12–14 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Aug 2026, 04:0213no change
10 Aug 2026, 18:4913first reading

Engagement

14 posts held, back to 12 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 1 pageof 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 14 posts for this entry, the most recent from 20 March 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
14
Links
1

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

20 Mar 2026, 16:57 UTC19 viewsread 12 August 2026
Forwarded from @ShiffyNyafOriginalPhoto

Партия адоптов! Вид: 🦦 Выдра Все по 10⭐ Все в наличии 💬 @Furry_Shiffy

20 Mar 2026, 13:18 UTC26 viewsread 12 August 2026
Photo

— Коммишка для Астры! (юз потерял) Был выполнен в декабре 2025.

11 Oct 2025, 11:03 UTCviews —

SHIFFY - YCHs, Commissions & Updates pinned «😈🔆🔆🔆🔆🔆🔆🔆🔆🔆🔆❗️😈 • Новый прайс лист! 🌟 Хед-иконка: 🔠🔠⭐️ Пример 1 Пример 2 Пример 3  Полно-рост: 🔠🔠⭐️ — за одного персонажа! Пример 1 Пример 2 Пример 3 Референсы: Симметричный: 🔠🔠⭐️ Зад, перед, и персонаж с одеждой Пример 1 Пример 2 Пример 3…»

11 Oct 2025, 10:57 UTC301 viewsread 12 August 2026

😈🔆🔆🔆🔆🔆🔆🔆🔆🔆🔆❗️😈 • Новый прайс лист! 🌟 Хед-иконка: 🔠🔠⭐️ Пример 1 Пример 2 Пример 3  Полно-рост: 🔠🔠⭐️ — за одного персонажа! Пример 1 Пример 2 Пример 3 Референсы: Симметричный: 🔠🔠⭐️ Зад, перед, и персонаж с одеждой Пример 1 Пример 2 Пример 3 Обычный: 🔠🔠⭐️ Зад, перед и одежда на вашем персонаже Пример 1 Пример 2 Пример 3 Многие примеры взяты с моего канала @ShiffyNyafOriginal! 😈

18 Aug 2025, 10:16 UTC164 viewsread 12 August 2026
Photo

—Референс для @Kkkkkkkuznets ! 🤩 Был выполнен: 14.08.25

21 Jul 2025, 12:21 UTC167 viewsread 12 August 2026
Photo

— Референс для @Rina_Lynx ! Был выполнен: 21.07.25

9 Jun 2025, 13:43 UTC637 viewsread 12 August 2026
Photo

— Коммишка для @KERRU_MALINA ! Был выполнен: 9.06.25

6 May 2025, 08:22 UTC492 viewsread 12 August 2026
Photo

— Коммишка для @EBENO4EK ! Был выполнен: 4.05.25

5 May 2025, 05:17 UTC390 viewsread 12 August 2026
Photo

— Коммишка для @Rhea_official12 ! :3 Был выполнен: 20.04.25

24 Mar 2025, 15:04 UTC702 viewsread 12 August 2026
Photo

— Примеры референсов: 1. — Семетричный Референс 2. — Обычный Референс 3. — Кастом Референс - персонаж по описанию или по готовой палитре

17 Mar 2025, 17:15 UTC606 viewsread 12 August 2026

— Сразу напоминаю: я не рисую птиц, насекомых, людей и ужастики. (потому что не умею их рисовать)

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

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

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

“SHIFFY - YCHs, Commissions & Updates” (@SHIFFYbah), 13 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/SHIFFYbah.

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.