BIZTRAC BETA
Uoppgitt

RØRNES INVEST AS

Org. no. 930292621 Limited company (AS) Tromsø Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −35,000
Equity NOK 1.7m
Incorporated 2022
Share capital NOK 220,000

Signals

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

RØRNES INVEST AS is registered as a limited company in Tromsø, Troms with organisation number 930292621. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2022. Registered share capital is NOK 220,000, divided into 500 shares. The company's stated purpose is: “Å eie aksjer i andre selskap og andre produkter/tjenester som naturlig hører sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −35,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −35,000
Equity
NOK 1.7m
Est. value
NOK 2.0m

Financial health · 2025

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

Who owns RØRNES INVEST AS?

ALEKSANDER SEM RØRNES
RØRNES INVEST AS
NOK 0 rev. · NOK −35,000 profit

RØRNES INVEST AS has 1 registered shareholder:

All shareholders and roles →

Which companies does RØRNES INVEST AS own?

RØRNES INVEST AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about RØRNES INVEST AS

Who owns RØRNES INVEST AS?

ALEKSANDER SEM RØRNES is the largest registered owner, with 100.0%.

What is the revenue of RØRNES INVEST AS?

RØRNES INVEST AS had revenue of NOK 0 in 2025.

Who is the general manager of RØRNES INVEST AS?

Aleksander Sem Rørnes is registered as general manager of RØRNES INVEST AS.

Where is RØRNES INVEST AS based?

RØRNES INVEST AS has its business address in Tromsdalen.

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.