BIZTRAC BETA
Rental and operating of own or leased real estate

ØRTANGEN AS

Org. no. 922343330 Limited company (AS) Vadsø Incorporated 2019 Active
Ownership graph ↗
Revenue 2024 NOK 956,000
Operating profit NOK 643,000
Equity NOK 1.2m
Incorporated 2019
Share capital NOK 2.5m

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

ØRTANGEN AS is registered as a limited company in Vadsø, Finnmark with organisation number 922343330. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2019. Registered share capital is NOK 2.5m, divided into 250000 shares. The company's stated purpose is: “Utleie av egen eller leid fast eiendom. Investering i og forvaltning av fast eiendom, andre formuesmidler og aksjer, samt utleie og utvikling av disse. Selskapet arbeider for egen regning og i samarbeide med andre selskaper og privatpersoner.”. The most recent filed accounts, for the 2024 financial year, show NOK 956,000 in revenue and NOK 643,000 in operating profit.

Key figures · 2024

Revenue
NOK 956,000
Operating profit
NOK 643,000
Equity
NOK 1.2m
Est. value
NOK 2.0m

Financial health · 2024

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

Who owns ØRTANGEN AS?

VADSØ NÆRINGSPARK AS
ØRTANGEN AS
NOK 956,000 rev. · NOK 643,000 profit

ØRTANGEN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ØRTANGEN AS

Who owns ØRTANGEN AS?

VADSØ NÆRINGSPARK AS is the largest registered owner, with 100.0%.

What is the revenue of ØRTANGEN AS?

ØRTANGEN AS had revenue of NOK 956,000 in 2024.

Where is ØRTANGEN AS based?

ØRTANGEN AS has its business address in Vadsø.

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.