biztrac. BETA
COMPANY REGISTER PROFILE
989229435 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Other real estate activities on a fee or contract basis

APELLA INVEST AS

Org. no. 989229435 Limited company (AS) Oslo Incorporated 2005 Active
Ownership graph ↗
Operating profit NOK −20,000
Equity NOK 17.8m
Incorporated 2005
Share capital NOK 250,000

Signals

2 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−20k kr).
  • Nylig endring 2026-09-28 Aksjekapital registrert 2026-09-28.

APELLA INVEST AS is registered as a limited company in Oslo, Oslo with organisation number 989229435. The business is classified under other real estate activities on a fee or contract basis (NACE 68.320). The company was incorporated in 2005. Registered share capital is NOK 250,000, divided into 250 shares. The company's stated purpose is: “Forvalte fast eiendom eller deler herav, eie, kjøpe eller selge andeler i selskaper som forvalter fast eiendom, konsulentvirksomhet og dessuten forvalte, eie, kjøpe og selge aksjer og fondsandeler og annen virksomhet som står i forbindelse med dette.”.

Key figures · 2025

Operating profit
NOK −20,000
▼ −47 %
Equity
NOK 17.8m
▼ −7 %
Est. value
NOK 14.5m

Financial health · 2025

Liquidity
3.59
Very good
Current assets ÷ current liabilities
Profitability
3.2%
Weak
Return on total assets
Solidity
89.9%
Very good
Equity as a share of total capital

Who owns APELLA INVEST AS?

APELLA INVEST AS
· NOK −20,000 profit

APELLA INVEST AS has 1 registered shareholder:

All shareholders and roles →

Which companies does APELLA INVEST AS own?

APELLA INVEST AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about APELLA INVEST AS

Who owns APELLA INVEST AS?

Jan Olav Karud is the largest registered owner, with 100.0%.

Where is APELLA INVEST AS based?

APELLA INVEST AS has its business address in Oslo.

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

Report a problem

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