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

NOCEBO HOLDING AS

Org. no. 921789688 Limited company (AS) Gjerdrum Incorporated 2018 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −11,000
Equity NOK 489,000
Incorporated 2018
Share capital NOK 31,000

Signals

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

NOCEBO HOLDING AS is registered as a limited company in Gjerdrum, Akershus with organisation number 921789688. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2018. Registered share capital is NOK 31,000, divided into 31000 shares. The company's stated purpose is: “Investere i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −11,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −11,000
Equity
NOK 489,000
Est. value
NOK 446,000

Financial health · 2025

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

Who owns NOCEBO HOLDING AS?

ALEKSANDER KIRKERUD RONESS
NOCEBO HOLDING AS
NOK 0 rev. · NOK −11,000 profit

NOCEBO HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does NOCEBO HOLDING AS own?

NOCEBO HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about NOCEBO HOLDING AS

Who owns NOCEBO HOLDING AS?

ALEKSANDER KIRKERUD RONESS is the largest registered owner, with 100.0%.

What is the revenue of NOCEBO HOLDING AS?

NOCEBO HOLDING AS had revenue of NOK 0 in 2025.

Where is NOCEBO HOLDING AS based?

NOCEBO HOLDING AS has its business address in Gjerdrum.

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.