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

SORGENFRI BYGG AS

Org. no. 927248328 Limited company (AS) Oslo Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 NOK 518,000
Operating profit NOK 51,000
Equity NOK 44,000
Incorporated 2021
Share capital NOK 30,000

SORGENFRI BYGG AS is registered as a limited company in Oslo, Oslo with organisation number 927248328. The business is classified under joinery installation (NACE 43.320). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Levere håndverkstjenester innen bygg og anlegg, og alt som står naturlig i sammenheng med dette som investering i fast eiendom.”. The most recent filed accounts, for the 2025 financial year, show NOK 518,000 in revenue and NOK 51,000 in operating profit.

Key figures · 2025

Revenue
NOK 518,000
▼ −8 %
Operating profit
NOK 51,000
▲ +313 %
Equity
NOK 44,000
▲ +543 %
Est. value
NOK 136,000

Financial health · 2025

Liquidity
1.95
Good
Current assets ÷ current liabilities
Profitability
80.7%
Very good
Return on total assets
Solidity
48.7%
Weak
Equity as a share of total capital

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

Who owns SORGENFRI BYGG AS?

SORGENFRI BYGG AS
NOK 518,000 rev. · NOK 51,000 profit

SORGENFRI BYGG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SORGENFRI BYGG AS

Who owns SORGENFRI BYGG AS?

Dario Pop is the largest registered owner, with 100.0%.

What is the revenue of SORGENFRI BYGG AS?

SORGENFRI BYGG AS had revenue of NOK 518,000 in 2025.

Who is the general manager of SORGENFRI BYGG AS?

Dario Pop is registered as general manager of SORGENFRI BYGG AS.

Where is SORGENFRI BYGG AS based?

SORGENFRI BYGG AS has its business address in Oslo.

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.