biztrac. BETA
COMPANY REGISTER PROFILE
920235859 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Other technical consultancy

OCELLARIS AS

Org. no. 920235859 Limited company (AS) Grimstad Incorporated 2018 Active
Revenue 2025 NOK 1.1m
Operating profit NOK −278,000
Equity NOK 220,000
Incorporated 2018
Share capital NOK 40,000

Signals

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

OCELLARIS AS is registered as a limited company in Grimstad, Agder with organisation number 920235859. The business is classified under other technical consultancy (NACE 71.129). The company was incorporated in 2018. Registered share capital is NOK 40,000, divided into 100 shares. The company's stated purpose is: “Yte tjenester innen maritim sektor, og drive investeringer og annen forretningsmessig virksomhet”. The most recent filed accounts, for the 2025 financial year, show NOK 1.1m in revenue and NOK −278,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.1m
▲ +14 %
Operating profit
NOK −278,000
▼ −119 %
Equity
NOK 220,000
▼ −75 %
Est. value
NOK 1.3m

Financial health · 2025

Liquidity
0.15
Not satisfactory
Current assets ÷ current liabilities
Profitability
-18.2%
Not satisfactory
Return on total assets
Solidity
15.8%
Satisfactory
Equity as a share of total capital

Who owns OCELLARIS AS?

OCELLARIS AS
NOK 1.1m rev. · NOK −278,000 profit

OCELLARIS AS has 1 registered shareholder:

All shareholders and roles →

Which companies does OCELLARIS AS own?

OCELLARIS AS holds stakes in 5 companies:

See the full ownership structure →

Frequently asked questions about OCELLARIS AS

Who owns OCELLARIS AS?

Alexander Lund is the largest registered owner, with 100.0%.

What is the revenue of OCELLARIS AS?

OCELLARIS AS had revenue of NOK 1.1m in 2025.

Where is OCELLARIS AS based?

OCELLARIS AS has its business address in Grimstad.

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.