biztrac. BETA
COMPANY REGISTER PROFILE
923993460 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Business and other management consultancy activities

SKRIMFJELL AS

Org. no. 923993460 Limited company (AS) Kongsberg Incorporated 2019 Active
Revenue 2025 NOK 0
Operating profit NOK −24,000
Equity NOK 73,000
Incorporated 2019
Share capital NOK 30,000

Signals

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

SKRIMFJELL AS is registered as a limited company in Kongsberg, Buskerud with organisation number 923993460. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Konsulentvirksomhet og teknologiutvikling.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −24,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −24,000
▼ −46 %
Equity
NOK 73,000
▼ −9 %
Est. value
NOK 119,000

Financial health · 2025

Liquidity
7.34
Very good
Current assets ÷ current liabilities
Profitability
-6.2%
Not satisfactory
Return on total assets
Solidity
86.4%
Weak
Equity as a share of total capital

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

Who owns SKRIMFJELL AS?

SKRIMFJELL AS
NOK 0 rev. · NOK −24,000 profit

SKRIMFJELL AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SKRIMFJELL AS

Who owns SKRIMFJELL AS?

Joar Bølstad is the largest registered owner, with 100.0%.

What is the revenue of SKRIMFJELL AS?

SKRIMFJELL AS had revenue of NOK 0 in 2025.

Who is the general manager of SKRIMFJELL AS?

Joar Bølstad is registered as general manager of SKRIMFJELL AS.

Where is SKRIMFJELL AS based?

SKRIMFJELL AS has its business address in Kongsberg.

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.