Telegram RegisterThe public register of Telegram
Telegram profile photo for Kapichu Web Services

Channel

Kapichu Web Services

@kapichu_news

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

68subscribers

+8 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1002794600364
TypeChannel
Username@kapichu_news
CreatedBetween 1 June 2025 and 30 September 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded10 August 2026
Last confirmed live16 September 2026
Measurements held6
Confirmed unchanged2 times, most recently 16 September 2026
On Telegramt.me/kapichu_news

Growth

6068646 August 2026 — 60 subscribers10 August 2026 — 60 subscribers15 August 2026 — 61 subscribers23 August 2026 — 62 subscribers29 August 2026 — 64 subscribers9 September 2026 — 68 subscribers6 August 20269 September 2026
6 measurements spanning 33 days, net +8. 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 59–69 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
9 Sept 2026, 00:2268+4
29 Aug 2026, 21:5764+2
23 Aug 2026, 12:1362+1
15 Aug 2026, 14:5661+1
10 Aug 2026, 05:0160no change
6 Aug 2026, 19:5060first reading

Engagement

19 posts held, back to 23 April 2026the 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 19 posts for this entry, the most recent from 3 August 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
21s
Average length
21s

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

393 reactions across 19 posts, in 15 distinct kinds. The most used accounts for 41.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 531909782820988361916341.5%
10426.5%
🔥6015.3%
225.60%
👍82.04%
🤣82.04%
❤‍🔥51.27%
👨‍💻41.02%
🥰41.02%
🏆30.763%
👏30.763%
🤡30.763%
👎20.509%
😨20.509%
😱20.509%

Custom emoji. One row above is a Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The count beside it is Telegram’s.

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 19 of the 19 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 393 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 19 most recent posts we hold, published 23 April 2026 to 3 August 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.

Telegram Stars

Stars received
1
across the posts below
Posts paid on
1
of 19 we hold a reading for · 5%
Most on one post
1
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @kapichu_news. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.

Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.

This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.

Counted over the 19 most recent posts we hold for this entry, published 23 April 2026 to 3 August 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.

Recent posts

3 Aug 2026, 16:30 UTC39 views18 reactionsread 10 August 2026
Photo

We have made two important updates to our platform🆕 • We have added an onboarding flow that helps new users quickly and easily get started, connect their store, and launch their first ad campaign✔️ • We have added a help center that contains all the needed documentation, FAQ, and instructions that new users would need✔️ This will help us optimize the onboarding process and customer support while we prepare to incre

custom 531909782820988361987👏3

Signed Тим Згейби

1 Aug 2026, 00:01 UTC57 views19 reactionsread 10 August 2026
Photo

Once again we have optimized the sync time from a long period of 11 mins down to 1 min🚀 You might ask, why did we have to do it again or why did the problem occur again? As our platform grows and we sync more data, we don't notice right away the difference in priority and rate limit between different different sets So when we add a new set to be synced regularly, only after some time when multiple stores have star

custom 5319097828209883619105👍4

Signed Тим Згейби

26 Jul 2026, 11:38 UTC106 views26 reactionsread 10 August 2026

🥰 Kapichu is now a little over one year old.. And honestly, a lot has happened in this one year.. We went from being a website development studio to becoming an e-commerce tech startup, building something the market hasn’t seen before During this year, we have: ✔️ Built and launched the Kapichu platform ✔️ Developed and tested multiple versions of our smart bidder ✔️ Connected 10 pilot stores, among them major Russ

custom 5319097828209883619128🔥4👎1🤡1

Signed Тим Згейби

15 Jul 2026, 13:57 UTC151 views24 reactionsread 10 August 2026

We are proud to announce that Kapichu is among the winners of the “Студенческий Стартап” grant of 1 Million rubles!🥳🔥 We have presented our technology, business model, and plans for the future to a jury from “Фонд содействия инновациям” This grant will have a great impact on our growth, especially at a relatively early stage like ours😌 Tune in for more coming🥰🥰

custom 53190978282098836191166👎1

Signed Тим Згейби

15 Jul 2026, 13:45 UTC143 views11 reactionsread 10 August 2026

We just received a GREAT NEWS🥳 Tune in

custom 531909782820988361972🔥2

Signed Тим Згейби

18 Jun 2026, 11:47 UTC210 views19 reactionsread 10 August 2026
Photo

🔄A little update Thanks to our pilots, we have managed to upgrade our smart bidder to its 3rd version✔️ We are testing the 3rd version, monitoring its performance and planning the next upgrade✔️ And also after receiving feedback from our pilots, we have added new features that make it easier to use our platform, like directly controlling ad campaign budget from campaigns' page, a more informative and user-friendly

custom 531909782820988361986🔥4🤡1

Signed Тим Згейби

19 May 2026, 23:19 UTC270 views25 reactionsread 10 August 2026
Forwarded from @fpmi_startup

Результаты стартап-трека 2026: 🥇Kapichu - ₽100к 🥈zlom.ai - ₽50к 🥉Cool Deal - ₽30к Приз зрительских симпатий (массажер MII GO): RinkVision Всех выступивших поздравляем с завершением трека, все молодцы! 👏

14custom 53190978282098836196🔥4🤡1

Signed Тим Згейби

19 May 2026, 23:09 UTC233 views21 reactionsread 10 August 2026

After a long time of no news.. Our bidder, again, is performing really well, we are expecting that by a week or two we have an estimate of how much it differs from other bidders😌 And we are first place winners in the Startup-Track accelerator, which we’ve been secretly part of for the past 3 months We’ve had checkpoints every month and because we were among the top 9 (we were actually first place😎) we were invited

12custom 53190978282098836196🔥3

Signed Тим Згейби

19 May 2026, 22:56 UTC216 views20 reactionsread 10 August 2026
Video

💪😌

custom 531909782820988361910❤‍🔥5🔥32

Signed Тим Згейби

19 May 2026, 22:56 UTC214 views19 reactionsread 10 August 2026
File

File, posted without a caption

custom 5319097828209883619106🔥3

Signed Тим Згейби

19 May 2026, 19:27 UTC177 views33 reactionsread 10 August 2026
Photo

Spoiler😌 We’ll write the update after we celebrate🍻

custom 53190978282098836191411🔥7🏆1

Signed Тим Згейби

7 May 2026, 20:33 UTC399 views23 reactionsread 10 August 2026

#vacancy Hello everyone! We’re looking for a Backend Developer to join 🥰Kapichu As you know, we launched our pilot program and we're getting closer to the public launch, so we're looking for a strong developer to help us with the increasing workload Required skills: Python, Flask, SQLAlchemy, Alembic, Celery, Redis Main focus: Backend development, API integrations, background jobs, data pipelines, production debu

custom 5319097828209883619126🔥5

Signed Тим Згейби

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

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.

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

“Kapichu Web Services” (@kapichu_news), 68 subscribers as measured 9 September 2026. Telegram Register, tgregister.com/channel/kapichu_news.

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.