BIZTRAC BETA
Uoppgitt

KJELDÅS AS

Org. no. 922156050 Limited company (AS) Holmestrand Incorporated 2019 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −12,000
Equity NOK 531,000
Incorporated 2019
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−12k kr).

KJELDÅS AS is registered as a limited company in Holmestrand, Vestfold with organisation number 922156050. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Investeringsvirksomhet, samt alt som hører naturlig til dette. Administrere andre selskaper eller forretningsvirksomheter av enhver art, direkte eller indirekte.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −12,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −12,000
Equity
NOK 531,000
Est. value
NOK 901,000

Financial health · 2024

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

Who owns KJELDÅS AS?

EIRIK KAPSTAD GRAN
KJELDÅS AS
NOK 0 rev. · NOK −12,000 profit

KJELDÅS AS has 1 registered shareholder:

All shareholders and roles →

Which companies does KJELDÅS AS own?

KJELDÅS AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about KJELDÅS AS

Who owns KJELDÅS AS?

EIRIK KAPSTAD GRAN is the largest registered owner, with 100.0%.

What is the revenue of KJELDÅS AS?

KJELDÅS AS had revenue of NOK 0 in 2024.

Who is the general manager of KJELDÅS AS?

Eirik Kapstad Gran is registered as general manager of KJELDÅS AS.

Where is KJELDÅS AS based?

KJELDÅS AS has its business address in Sande I Vestfold.

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.