BIZTRAC BETA
Rental and operating of own or leased real estate

GAMMELVEIEN 22 AS

Org. no. 926707426 Limited company (AS) Vågan Incorporated 2021 Active
Ownership graph ↗
Revenue 2024 NOK 21.0m
Operating profit NOK −4.9m
Equity NOK −3.8m
Incorporated 2021
Share capital NOK 3.0m

Signals

3 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−3,8 mill kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−4,9 mill kr).
  • Nylig endring 2026-02-27 Adresseendring registrert 2026-02-27.

GAMMELVEIEN 22 AS is registered as a limited company in Vågan, Nordland with organisation number 926707426. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2021. Registered share capital is NOK 3.0m, divided into 100200 shares. The company's stated purpose is: “Kjøp og utvikling av eiendom for utleie og videresalg.”. The most recent filed accounts, for the 2024 financial year, show NOK 21.0m in revenue and NOK −4.9m in operating profit.

Key figures · 2024

Revenue
NOK 21.0m
Operating profit
NOK −4.9m
Equity
NOK −3.8m

Financial health · 2024

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

Solidity capped at Weak because equity is below NOK 100,000.

Who owns GAMMELVEIEN 22 AS?

SALTERIET HOLDING AS
GAMMELVEIEN 22 AS
NOK 21.0m rev. · NOK −4.9m profit

GAMMELVEIEN 22 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about GAMMELVEIEN 22 AS

Who owns GAMMELVEIEN 22 AS?

SALTERIET HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of GAMMELVEIEN 22 AS?

GAMMELVEIEN 22 AS had revenue of NOK 21.0m in 2024.

Where is GAMMELVEIEN 22 AS based?

GAMMELVEIEN 22 AS has its business address in Henningsvær.

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.