biztrac. BETA
COMPANY REGISTER PROFILE
921213352 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Accounting and bookkeeping

TYSNES RÅD & REGNSKAP AS

Org. no. 921213352 Limited company (AS) Tysnes Incorporated 2018 Active
Ownership graph ↗
Revenue 2025 NOK 2.3m
Operating profit NOK 37,000
Equity NOK 624,000
Incorporated 2018
Share capital NOK 30,000

TYSNES RÅD & REGNSKAP AS is registered as a limited company in Tysnes, Vestland with organisation number 921213352. The business is classified under accounting and bookkeeping (NACE 69.202). The company was incorporated in 2018. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Regnskapstjenester og økonomisk rådgivning.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.3m in revenue and NOK 37,000 in operating profit.

Former names: OK&E AS

Key figures · 2025

Revenue
NOK 2.3m
▲ +4 %
Operating profit
NOK 37,000
▼ −84 %
Equity
NOK 624,000
▲ +1 %
Est. value
NOK 609,000

Financial health · 2025

Liquidity
2.34
Very good
Current assets ÷ current liabilities
Profitability
3.4%
Weak
Return on total assets
Solidity
57.3%
Very good
Equity as a share of total capital

Who owns TYSNES RÅD & REGNSKAP AS?

TYSNES RÅD & REGNSKAP AS
NOK 2.3m rev. · NOK 37,000 profit

TYSNES RÅD & REGNSKAP AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about TYSNES RÅD & REGNSKAP AS

Who owns TYSNES RÅD & REGNSKAP AS?

Elisabeth Sandven is the largest registered owner, with 40.0%.

What is the revenue of TYSNES RÅD & REGNSKAP AS?

TYSNES RÅD & REGNSKAP AS had revenue of NOK 2.3m in 2025.

Who is the general manager of TYSNES RÅD & REGNSKAP AS?

Ole-Kristian Dalen is registered as general manager of TYSNES RÅD & REGNSKAP AS.

Where is TYSNES RÅD & REGNSKAP AS based?

TYSNES RÅD & REGNSKAP AS has its business address in Uggdal.

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.