BIZTRAC BETA
Rental and operating of own or leased real estate

NYRØ INVEST AS

Org. no. 924403136 Limited company (AS) Ørsta Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 35,000
Operating profit NOK −144,000
Equity NOK 9.9m
Incorporated 2020
Share capital NOK 60,000

Signals

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

NYRØ INVEST AS is registered as a limited company in Ørsta, Møre og Romsdal with organisation number 924403136. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2020. Registered share capital is NOK 60,000, divided into 60000 shares. The company's stated purpose is: “Investeringer, eiendomsutvikling og utleie av eiendom, og annet som naturlig faller sammen med dette, samt å eie og delta i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 35,000 in revenue and NOK −144,000 in operating profit.

Key figures · 2025

Revenue
NOK 35,000
Operating profit
NOK −144,000
Equity
NOK 9.9m
Est. value
NOK 8.9m

Financial health · 2025

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

Who owns NYRØ INVEST AS?

STIAN NYRØ
NYRØ INVEST AS
NOK 35,000 rev. · NOK −144,000 profit

NYRØ INVEST AS has 1 registered shareholder:

All shareholders and roles →

Which companies does NYRØ INVEST AS own?

NYRØ INVEST AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about NYRØ INVEST AS

Who owns NYRØ INVEST AS?

STIAN NYRØ is the largest registered owner, with 100.0%.

What is the revenue of NYRØ INVEST AS?

NYRØ INVEST AS had revenue of NOK 35,000 in 2025.

Where is NYRØ INVEST AS based?

NYRØ INVEST AS has its business address in Ørsta.

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.