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

FOSNA REGNSKAP AS

Org. no. 996410714 Limited company (AS) Kristiansund Incorporated 2011 Active
Revenue 2025 NOK 7.3m
Operating profit NOK 1.6m
Equity NOK 619,000
Incorporated 2011
Share capital NOK 500,000

FOSNA REGNSKAP AS is registered as a limited company in Kristiansund, Møre og Romsdal with organisation number 996410714. The business is classified under accounting and bookkeeping (NACE 69.202). The company was incorporated in 2011. Registered share capital is NOK 500,000, divided into 5000 shares. The company's stated purpose is: “Regnskapsføring, økonomisk rådgivning samt det som naturlig hører til dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 7.3m in revenue and NOK 1.6m in operating profit.

Former names: SØR-TRØNDELAG EIENDOMSMEGLING AS, BOLIGHUSET INVEST AS

Key figures · 2025

Revenue
NOK 7.3m
▲ +109 %
Operating profit
NOK 1.6m
▲ +288 %
Equity
NOK 619,000
▲ +16 %
Est. value
NOK 5.6m

Financial health · 2025

Liquidity
1.20
Satisfactory
Current assets ÷ current liabilities
Profitability
65.3%
Very good
Return on total assets
Solidity
18.0%
Satisfactory
Equity as a share of total capital

Who owns FOSNA REGNSKAP AS?

FOSNA REGNSKAP AS
NOK 7.3m rev. · NOK 1.6m profit

FOSNA REGNSKAP AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about FOSNA REGNSKAP AS

Who owns FOSNA REGNSKAP AS?

NOTAR AS is the largest registered owner, with 50.0%.

What is the revenue of FOSNA REGNSKAP AS?

FOSNA REGNSKAP AS had revenue of NOK 7.3m in 2025.

Who is the general manager of FOSNA REGNSKAP AS?

Fredrik Garshol Eeg is registered as general manager of FOSNA REGNSKAP AS.

Where is FOSNA REGNSKAP AS based?

FOSNA REGNSKAP AS has its business address in Kristiansund N.

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.