Viken Fiber's tech stack
What does Viken Fiber use?
Viken Fiber (vikenfiber.no) uses at least 16 tools we can see from public records, including WP Engine for hosting, Google Analytics for analytics, WordPress for its website and SendGrid for email delivery. Last checked .
- Industry
- Telecommunications
- Based in
- Norway
- Tools found
- 16
- Categories
- 9
- Layers
- 5 of 5
- Last checked
- Oct 2026
Viken Fiber's stack, layer by layer
Each tool links to the other companies we've found using it. The label says what kind of public trace gave it away.
Edge & Hosting
1 tool, where the bytes are served from
Hosting & Cloud
Application
1 tool, what the product is built with
Frontend
Data & Observability
4 tools, what they measure and store
Flags & Experiments
Go-to-market
7 tools, how they find and keep customers
Website & CMS
Marketing
Company Ops
3 tools, what the team runs on day to day
Email Delivery
Security & Compliance
Viken Fiber tech stack FAQ
What tools does Viken Fiber use?
We've found 16 tools at Viken Fiber (vikenfiber.no). Edge & Hosting: WP Engine. Application: jQuery. Data & Observability: Google Analytics, Google Tag Manager and Hotjar. Go-to-market: Meta Pixel, Google Ads and WordPress. Company Ops: SendGrid, reCAPTCHA and Cookiebot. Last checked October 3, 2026.
What cloud does Viken Fiber run on?
Viken Fiber uses WP Engine for hosting. We found WP Engine through custom domain and website code.
What analytics tools does Viken Fiber use?
Viken Fiber uses Google Analytics, Google Tag Manager and Hotjar for analytics. We found Google Analytics through website code.
What CMS does Viken Fiber use?
Viken Fiber uses WordPress and Rank Math for its website. We found WordPress through website code.
Does Viken Fiber use Google Analytics?
Yes. We found Google Analytics at Viken Fiber through website code. Google Analytics is used by 89,943 companies we track.
How does runsonwhat know what Viken Fiber uses?
We read public traces only: Viken Fiber's DNS and email records, certificate logs, the code its website loads, and published subprocessor lists. A tool is listed only when a direct record backs it up. DNS is rechecked weekly and the website monthly.
We read public traces only: DNS and email records, certificate logs, website code and published subprocessor lists. A tool is listed when a direct record backs it up, and dropped when a recheck no longer finds it. Is this your company? See how to opt out.