biztrac. BETA
COMPANY REGISTER PROFILE
933421945 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Joinery installation

FJORDVIRKE AS

Org. no. 933421945 Limited company (AS) Asker Incorporated 2024 Active
Revenue 2025 NOK 1.0m
Operating profit NOK −25,000
Equity NOK 47,000
Incorporated 2024
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−25k kr).

FJORDVIRKE AS is registered as a limited company in Asker, Akershus with organisation number 933421945. The business is classified under joinery installation (NACE 43.320). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Renovasjon langs kysten. Virke langs kysten. Servicetjenester langs kysten.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.0m in revenue and NOK −25,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.0m
▲ +207 %
Operating profit
NOK −25,000
▼ −138 %
Equity
NOK 47,000
▼ −39 %
Est. value
NOK 53,000

Financial health · 2025

Liquidity
1.75
Good
Current assets ÷ current liabilities
Profitability
-2.7%
Not satisfactory
Return on total assets
Solidity
5.1%
Weak
Equity as a share of total capital

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

Who owns FJORDVIRKE AS?

FJORDVIRKE AS
NOK 1.0m rev. · NOK −25,000 profit

FJORDVIRKE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about FJORDVIRKE AS

Who owns FJORDVIRKE AS?

Håkon Boye Berven is the largest registered owner, with 100.0%.

What is the revenue of FJORDVIRKE AS?

FJORDVIRKE AS had revenue of NOK 1.0m in 2025.

Who is the general manager of FJORDVIRKE AS?

Håkon Boye Berven is registered as general manager of FJORDVIRKE AS.

Where is FJORDVIRKE AS based?

FJORDVIRKE AS has its business address in Nesøya.

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.