BIZTRAC BETA
Development of building projects

SØRLIE BYGG AS

Org. no. 921182643 Limited company (AS) Sarpsborg Incorporated 2018 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −46,000
Equity NOK 60.9m
Incorporated 2018
Share capital NOK 250,000

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−46k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

SØRLIE BYGG AS is registered as a limited company in Sarpsborg, Østfold with organisation number 921182643. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2018. Registered share capital is NOK 250,000, divided into 100 shares. The company's stated purpose is: “Kjøpe og selge aksjer og annen virksomhet som er tilknyttet dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −46,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −46,000
Equity
NOK 60.9m
Est. value
NOK 53.4m

Financial health · 2024

Liquidity
1.49
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
96.0%
Very good
Equity as a share of total capital

Who owns SØRLIE BYGG AS?

ARNFINN SØRLIE
SØRLIE BYGG AS
NOK 0 rev. · NOK −46,000 profit

SØRLIE BYGG AS has 3 registered shareholders:

All shareholders and roles →

Which companies does SØRLIE BYGG AS own?

SØRLIE BYGG AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about SØRLIE BYGG AS

Who owns SØRLIE BYGG AS?

ARNFINN SØRLIE is the largest registered owner, with 68.0%.

What is the revenue of SØRLIE BYGG AS?

SØRLIE BYGG AS had revenue of NOK 0 in 2024.

Where is SØRLIE BYGG AS based?

SØRLIE BYGG AS has its business address in Sarpsborg.

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.