BIZTRAC BETA
Rental and operating of own or leased real estate

OBELIX INVEST AS

Org. no. 917148759 Limited company (AS) Tromsø Incorporated 2016 Active
Ownership graph ↗
Revenue 2024 NOK 1.5m
Operating profit NOK 431,000
Equity NOK 411,000
Incorporated 2016
Share capital NOK 100,000

OBELIX INVEST AS is registered as a limited company in Tromsø, Troms with organisation number 917148759. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2016. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Investering i aksjer og fast eiendom, samt annen virksomhet som står i naturlig tilknytning til dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.5m in revenue and NOK 431,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.5m
Operating profit
NOK 431,000
Equity
NOK 411,000
Est. value
NOK 1.4m

Financial health · 2024

Liquidity
1.17
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
20.6%
Good
Equity as a share of total capital

Who owns OBELIX INVEST AS?

VIDAR ANDERSEN
OBELIX INVEST AS
NOK 1.5m rev. · NOK 431,000 profit

OBELIX INVEST AS has 1 registered shareholder:

All shareholders and roles →

Which companies does OBELIX INVEST AS own?

OBELIX INVEST AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about OBELIX INVEST AS

Who owns OBELIX INVEST AS?

VIDAR ANDERSEN is the largest registered owner, with 100.0%.

What is the revenue of OBELIX INVEST AS?

OBELIX INVEST AS had revenue of NOK 1.5m in 2024.

Who is the general manager of OBELIX INVEST AS?

Vidar Andersen is registered as general manager of OBELIX INVEST AS.

Where is OBELIX INVEST AS based?

OBELIX INVEST AS has its business address in Tromsø.

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.