Bot

Свайпач

@dvachmatchbot

2 usernames

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

17,842monthly users

-705 since we began measuring on 5 August 2026

Risers and fallers across the register · movement among entries of 10,000–31,623.

Register entry

Telegram ID	8448473818
Type	Bot
Usernames	@datemeplz @dvachmatchbot
First recorded	17 August 2026
Last confirmed live	25 August 2026
Measurements held	27
Confirmed unchanged	1 time, most recently 25 August 2026
On Telegram	t.me/dvachmatchbot

Growth

27 measurements spanning 20 days, net -705. 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 17,598–18,759 and does not start at zero.

Measurement log — every monthly users count we have recorded, most recent 20 of 27
Measured (UTC)	Monthly users	Change
25 Aug 2026, 23:14	17,842	no change
25 Aug 2026, 18:49	17,842	+79
25 Aug 2026, 00:47	17,763	no change
24 Aug 2026, 17:04	17,763	+31
23 Aug 2026, 11:08	17,732	no change
23 Aug 2026, 00:23	17,732	-53
19 Aug 2026, 14:13	17,785	no change
18 Aug 2026, 19:13	17,785	-32
17 Aug 2026, 20:27	17,817	-90
17 Aug 2026, 16:30	17,907	+90
17 Aug 2026, 11:43	17,817	-90
15 Aug 2026, 17:05	17,907	no change
14 Aug 2026, 12:05	17,907	-66
14 Aug 2026, 03:58	17,973	no change
13 Aug 2026, 02:15	17,973	-38
12 Aug 2026, 19:47	18,011	no change
12 Aug 2026, 00:14	18,011	-65
10 Aug 2026, 22:48	18,076	no change
10 Aug 2026, 14:37	18,076	-547
9 Aug 2026, 13:11	18,623	first reading

Engagement

No post feed to measure. Telegram publishes a readable post stream for channels, not for bots, so views, reactions and engagement rates do not exist for this entry — they are not missing, pending or withheld. The register records what this handle is and what it resolves to.

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.

Двач
@dvachannel · 937,7446 posts

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

“Свайпач” (@dvachmatchbot), 17,842 monthly users as measured 25 August 2026. Telegram Register, tgregister.com/channel/dvachmatchbot.

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.