BIZTRAC BETA
COMPANY REGISTER PROFILE
933353915 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Uoppgitt

GALEOS AS

Org. no. 933353915 Limited company (AS) Nittedal Incorporated 2023 Active
Ownership graph ↗
Operating profit NOK −28,000
Equity NOK 3.4m
Incorporated 2023
Share capital NOK 30,000

Signals

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

GALEOS AS is registered as a limited company in Nittedal, Akershus with organisation number 933353915. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Deltakelse i andre selskaper, samt investering i aksjer og andre verdipapirer.”.

Key figures · 2025

Operating profit
NOK −28,000
▼ −34 %
Equity
NOK 3.4m
▼ −40 %
Est. value
NOK 3.9m

Financial health · 2025

Liquidity
0.64
Weak
Current assets ÷ current liabilities
Profitability
-0.2%
Not satisfactory
Return on total assets
Solidity
83.7%
Very good
Equity as a share of total capital

Who owns GALEOS AS?

GALEOS AS
· NOK −28,000 profit

GALEOS AS has 1 registered shareholder:

All shareholders and roles →

Which companies does GALEOS AS own?

GALEOS AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about GALEOS AS

Who owns GALEOS AS?

KIM ARE BIRKELI LIVGARD is the largest registered owner, with 100.0%.

Where is GALEOS AS based?

GALEOS AS has its business address in Hagan.

Property

Business address c/o Kim Are Birkeli Livgard Ørekyteveien 64, 1481 Hagan
Cadastral unit 3232-36/35/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.