biztrac. BETA
COMPANY REGISTER PROFILE
920500188 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Uoppgitt

LANGØYA UTLEIE AS

Org. no. 920500188 Limited company (AS) Vågan Incorporated 2018 Active
Revenue 2025 NOK 3.1m
Operating profit NOK 1.7m
Equity NOK 767,000
Incorporated 2018
Share capital NOK 3.4m

Signals

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

LANGØYA UTLEIE AS is registered as a limited company in Vågan, Nordland with organisation number 920500188. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2018. Registered share capital is NOK 3.4m, divided into 30000 shares. The company's stated purpose is: “Investeringer i andre selskaper, aksjer, verdipapirer, fast eiendom og alt som er forbundet med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.1m in revenue and NOK 1.7m in operating profit.

Former names: PARKGATA BOLIG AS

Key figures · 2025

Revenue
NOK 3.1m
▲ +73 %
Operating profit
NOK 1.7m
▲ +251 %
Equity
NOK 767,000
▲ +139 %
Est. value
NOK 2.0m

Financial health · 2025

Liquidity
8.49
Very good
Current assets ÷ current liabilities
Profitability
10.2%
Good
Return on total assets
Solidity
7.6%
Weak
Equity as a share of total capital

Who owns LANGØYA UTLEIE AS?

LANGØYA UTLEIE AS
NOK 3.1m rev. · NOK 1.7m profit

LANGØYA UTLEIE AS has 1 registered shareholder:

All shareholders and roles →

Group structure

LANGØYA UTLEIE AS er morselskap for 10 datterselskaper:

Frequently asked questions about LANGØYA UTLEIE AS

Who owns LANGØYA UTLEIE AS?

LANGØYA INVEST AS is the largest registered owner, with 100.0%.

What is the revenue of LANGØYA UTLEIE AS?

LANGØYA UTLEIE AS had revenue of NOK 3.1m in 2025.

Where is LANGØYA UTLEIE AS based?

LANGØYA UTLEIE AS has its business address in Svolvær.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.