biztrac. BETA
COMPANY REGISTER PROFILE
920571743 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Translation and interpretation activities

SPRÅKSENTERET AS

Org. no. 920571743 Limited company (AS) Tromsø Incorporated 2018 Active
Revenue 2025 NOK 9.1m
Operating profit NOK 1.1m
Equity NOK 5.0m
Incorporated 2018
Employees 5
Share capital NOK 30,000

SPRÅKSENTERET AS is registered as a limited company in Tromsø, Troms with organisation number 920571743. The business is classified under translation and interpretation activities (NACE 74.300). The company was incorporated in 2018 and has 5 registered employees. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Oversettelses- og tolkevirksomhet. Selskapet skal også kunne delta i likelydende virksomheter med samme formål.”. The most recent filed accounts, for the 2025 financial year, show NOK 9.1m in revenue and NOK 1.1m in operating profit.

Key figures · 2025

Revenue
NOK 9.1m
▼ −14 %
Operating profit
NOK 1.1m
▲ +99 %
Equity
NOK 5.0m
▲ +20 %
Est. value
NOK 8.6m

Financial health · 2025

Liquidity
2.00
Very good
Current assets ÷ current liabilities
Profitability
15.5%
Very good
Return on total assets
Solidity
70.6%
Very good
Equity as a share of total capital

Who owns SPRÅKSENTERET AS?

SPRÅKSENTERET AS
NOK 9.1m rev. · NOK 1.1m profit

SPRÅKSENTERET AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SPRÅKSENTERET AS

Who owns SPRÅKSENTERET AS?

Kine Aileen Stark Hansen is the largest registered owner, with 100.0%.

What is the revenue of SPRÅKSENTERET AS?

SPRÅKSENTERET AS had revenue of NOK 9.1m in 2025.

Who is the general manager of SPRÅKSENTERET AS?

Kine Aileen Stark Hansen is registered as general manager of SPRÅKSENTERET AS.

Where is SPRÅKSENTERET AS based?

SPRÅKSENTERET AS has its business address in Tromsø.

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

Report a problem

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