BIZTRAC BETA
COMPANY REGISTER PROFILE
999505422 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 15.06.2026
Business and other management consultancy activities

FOSNAVÅG REGNSKAP AS

Org. no. 999505422 Limited company (AS) Herøy Incorporated 2013 Active
Ownership graph ↗
Revenue 2025 NOK 17,000
Operating profit NOK 7,000
Equity NOK 31,000
Incorporated 2013
Share capital NOK 40,000

FOSNAVÅG REGNSKAP AS is registered as a limited company in Herøy, Møre og Romsdal with organisation number 999505422. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2013. Registered share capital is NOK 40,000, divided into 40000 shares. The company's stated purpose is: “Økonomi- og konsulenttjenester og det som hører til, samt investering i aksjer, fond o.l.”. The most recent filed accounts, for the 2025 financial year, show NOK 17,000 in revenue and NOK 7,000 in operating profit.

Former names: FOSNAVÅG BYGGSERVICE AS

Key figures · 2025

Revenue
NOK 17,000
Operating profit
NOK 7,000
Equity
NOK 31,000
Est. value
NOK 43,000

Financial health · 2025

Liquidity
10.92
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
90.8%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns FOSNAVÅG REGNSKAP AS?

ROBERT SCHJELDERUP
FOSNAVÅG REGNSKAP AS
NOK 17,000 rev. · NOK 7,000 profit

FOSNAVÅG REGNSKAP AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about FOSNAVÅG REGNSKAP AS

Who owns FOSNAVÅG REGNSKAP AS?

ROBERT SCHJELDERUP is the largest registered owner, with 100.0%.

What is the revenue of FOSNAVÅG REGNSKAP AS?

FOSNAVÅG REGNSKAP AS had revenue of NOK 17,000 in 2025.

Where is FOSNAVÅG REGNSKAP AS based?

FOSNAVÅG REGNSKAP AS has its business address in Fosnavåg.

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.