Products

トロクレチケット

Ticket booking system built for small-theater performances.

trkr.jp Business Operations / Event Management & Ticketing

AI Benchmark
Desktop
Mobile
Monthly visits
6.4K
Down25.0%MoMOct 2026
Public revenue
Undisclosed
No public revenue evidence yet
Entry price
$14.74/mo
Lower than 66% of peersNiche median $21.59/mo
Creators
Unlinked
No verified creators
Launched
3y ago
2023-06-15 · Est.

Traffic

Monthly visitsData through Oct 2026

Marketing moves

Launches, search & content, referrals, promotions
  • New product launchLaunch

    Jun 15, 2023 · 3y agoWebsite

Traffic sources

Oct 2026

Traffic breakdown

Channels

  • Direct80%
  • Organic Search10%
  • Referrals5%
  • Social4%

Countries

  • Japan100%

Search

Domain authority —Domain registered 2023-06-15

KeywordMonthly volume
トロクレチケット210
命どぅ宝 演劇160
たつの演劇祭2026 in 龍野150
たつの演劇祭2026150
トロクレ150

Traffic data: Vaneform

Pricing

無料プラン
Unknown
500席 · 公演終了から 7日目まで
有料プラン
月額2,200円・税込
3,000席 · 公演終了から 90日目まで

Trial: None · Observed 2026-11-05 · Source page

Entry price $14.74/mo, Lower than 66% of peers; “Event Management & Ticketing” median is $21.59/mo.View pricing benchmark

Pages & changes

Tracked since 2026-11-04

Key pages

Weekly snapshots
Home
trkr.jp/ Snapshot 2026-11-06

Changes

No pricing, plan, or positioning changes detected since tracking started.

Questions & evidence

How much does トロクレチケット cost?
無料プラン: Unknown; 有料プラン: 月額2,200円・税込. Observed 2026-11-05. Check the source for current billing terms, usage limits and taxes.Source
How much website traffic does トロクレチケット get?
Vaneform estimates 6.4K website visits in 2026-10. Visits can include repeat visits; this estimate measures web traffic separately from paying customers or revenue.Source
What is トロクレチケット and what platforms does it support?
トロクレチケット is catalogued under Event Management & Ticketing: Ticket booking system built for small-theater performances. Supported platforms: Web.

Related products in this category

Business Operations / Event Management & Ticketing

These products share a catalog category. Compare customer tasks, features and deployment requirements before treating them as alternatives.