BIZTRAC BETA
Development of building projects

SKRIKARLIA UTVIKLING AS

Org. no. 930624144 Limited company (AS) Sigdal Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 1.7m
Operating profit NOK 340,000
Equity NOK 481,000
Incorporated 2022
Share capital NOK 30,000

SKRIKARLIA UTVIKLING AS is registered as a limited company in Sigdal, Buskerud with organisation number 930624144. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Utvikling, drift, kjøp og salg av fast eiendom, samt alt som står i forbindelse med dette, herunder deltagelse i andre selskap.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.7m in revenue and NOK 340,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.7m
Operating profit
NOK 340,000
Equity
NOK 481,000
Est. value
NOK 1.2m

Financial health · 2025

Liquidity
1.80
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
44.5%
Very good
Equity as a share of total capital

Who owns SKRIKARLIA UTVIKLING AS?

NEDRE KOPSENG HOLDING AS
SKRIKARLIA UTVIKLING AS
NOK 1.7m rev. · NOK 340,000 profit

SKRIKARLIA UTVIKLING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SKRIKARLIA UTVIKLING AS

Who owns SKRIKARLIA UTVIKLING AS?

NEDRE KOPSENG HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of SKRIKARLIA UTVIKLING AS?

SKRIKARLIA UTVIKLING AS had revenue of NOK 1.7m in 2025.

Who is the general manager of SKRIKARLIA UTVIKLING AS?

Åse Lene Blegeberg Eckhoff is registered as general manager of SKRIKARLIA UTVIKLING AS.

Where is SKRIKARLIA UTVIKLING AS based?

SKRIKARLIA UTVIKLING AS has its business address in Eggedal.

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.