BIZTRAC BETA
Activities of call centres

SERVICE TELEFONEN AS

Org. no. 988350346 Limited company (AS) Sør-Odal Incorporated 2005 Active
Ownership graph ↗
Revenue 2025 NOK 6.7m
Operating profit NOK 741,000
Equity NOK 868,000
Incorporated 2005
Employees 12
Share capital NOK 100,000

SERVICE TELEFONEN AS is registered as a limited company in Sør-Odal, Innlandet with organisation number 988350346. The business is classified under activities of call centres (NACE 82.200). The company was incorporated in 2005 and has 12 registered employees. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Yte IKT-tjenester til privat og offentlig sektor, samt alt som herved står i forbindelse med dette, herunder deltakelse i andre selskaper med samme eller lignende formål.”. The most recent filed accounts, for the 2025 financial year, show NOK 6.7m in revenue and NOK 741,000 in operating profit.

Key figures · 2025

Revenue
NOK 6.7m
Operating profit
NOK 741,000
Equity
NOK 868,000
Est. value
NOK 3.5m

Financial health · 2025

Liquidity
1.68
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
38.9%
Good
Equity as a share of total capital

Who owns SERVICE TELEFONEN AS?

VERONICA TETTENBORN
SERVICE TELEFONEN AS
NOK 6.7m rev. · NOK 741,000 profit

SERVICE TELEFONEN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SERVICE TELEFONEN AS

Who owns SERVICE TELEFONEN AS?

VERONICA TETTENBORN is the largest registered owner, with 100.0%.

What is the revenue of SERVICE TELEFONEN AS?

SERVICE TELEFONEN AS had revenue of NOK 6.7m in 2025.

Who is the general manager of SERVICE TELEFONEN AS?

Leo Kværner is registered as general manager of SERVICE TELEFONEN AS.

Where is SERVICE TELEFONEN AS based?

SERVICE TELEFONEN AS has its business address in Skarnes.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 15.06.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.