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

SKÅFONN AS

Org. no. 930481963 Limited company (AS) Ås Incorporated 2022 Active
Ownership graph ↗
Operating profit NOK −21,000
Equity NOK 2.3m
Incorporated 2022
Share capital NOK 43,000

Signals

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

SKÅFONN AS is registered as a limited company in Ås, Akershus with organisation number 930481963. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2022. Registered share capital is NOK 43,000, divided into 1000 shares. The company's stated purpose is: “Eie aksjer og verdipapirer.”.

Key figures · 2025

Operating profit
NOK −21,000
▼ −68 %
Equity
NOK 2.3m
▲ +14 %
Est. value
NOK 3.1m

Financial health · 2025

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

Who owns SKÅFONN AS?

SKÅFONN AS
· NOK −21,000 profit

SKÅFONN AS has 1 registered shareholder:

All shareholders and roles →

Which companies does SKÅFONN AS own?

SKÅFONN AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about SKÅFONN AS

Who owns SKÅFONN AS?

ØYSTEIN HAUKELIDSÆTER is the largest registered owner, with 100.0%.

Where is SKÅFONN AS based?

SKÅFONN AS has its business address in Ski.

Property

Business address Nygårdsveien 26, 1423 Ski
Cadastral unit 3218-103/55/0/0
Building Annen industribygning · 1 unit

14 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.