BIZTRAC BETA
COMPANY REGISTER PROFILE
920672752 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Other captive investment companies

K ELD AS

Org. no. 920672752 Limited company (AS) Stord Incorporated 2018 Active
Ownership graph ↗
Operating profit NOK −11,000
Equity NOK 235,000
Incorporated 2018
Share capital NOK 30,000

Signals

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

K ELD AS is registered as a limited company in Stord, Vestland with organisation number 920672752. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2018. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Investering i aksjer og andre finansielle eiendeler.”.

Key figures · 2025

Operating profit
NOK −11,000
▼ −23 %
Equity
NOK 235,000
▼ −5 %
Est. value
NOK 215,000

Financial health · 2025

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

Who owns K ELD AS?

K ELD AS
· NOK −11,000 profit

K ELD AS has 1 registered shareholder:

All shareholders and roles →

Which companies does K ELD AS own?

K ELD AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about K ELD AS

Who owns K ELD AS?

KAROLINE ELDØY is the largest registered owner, with 100.0%.

Where is K ELD AS based?

K ELD AS has its business address in Stord.

Property

Business address Håvåsen 2, 5416 Stord
Cadastral unit 4614-26/267/0/0
Building Enebolig · 1 unit

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.