BIZTRAC BETA
COMPANY REGISTER PROFILE
927053535 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Uoppgitt

SADF AS

Org. no. 927053535 Limited company (AS) Haugesund Incorporated 2021 Active
Ownership graph ↗
Operating profit NOK −5,000
Equity NOK 860,000
Incorporated 2021
Share capital NOK 30,000

Signals

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

SADF AS is registered as a limited company in Haugesund, Rogaland with organisation number 927053535. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 130 shares. The company's stated purpose is: “Investeringsvirksomhet.”.

Key figures · 2025

Operating profit
NOK −5,000
▼ −3686 %
Equity
NOK 860,000
▲ +13 %
Est. value
NOK 1.1m

Financial health · 2025

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

Who owns SADF AS?

SADF AS
· NOK −5,000 profit

SADF AS has 1 registered shareholder:

All shareholders and roles →

Which companies does SADF AS own?

SADF AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about SADF AS

Who owns SADF AS?

KARL CHRISTIAN GRØNHAUG is the largest registered owner, with 100.0%.

Where is SADF AS based?

SADF AS has its business address in Haugesund.

Property

Business address Nauthaug 9, 5518 Haugesund
Cadastral unit 1106-24/352/0/0
Building Tomannsbolig, horisontaldelt · 2 units

4 companies are registered at this address.

The address this company is registered at, from the company register and matched against the cadastre. It does not say who owns the property — a company may be a tenant, and the address is often its accountant's. Source: Brønnøysundregistrene and © Kartverket.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 02.09.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.