biztrac. BETA
COMPANY REGISTER PROFILE
929030125 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Development of building projects

GAMLEVEGEN 222 AS

Org. no. 929030125 Limited company (AS) Lillehammer Incorporated 2022 Active
Ownership graph ↗
Operating profit NOK −17,000
Equity NOK −22,000
Incorporated 2022
Share capital NOK 30,000

Signals

3 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−22k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−17k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

GAMLEVEGEN 222 AS is registered as a limited company in Lillehammer, Innlandet with organisation number 929030125. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Utvikling og utbygging, markedsføring og salg av fast eiendom, samt deltakelse i annen virksomhet med samme formål.”.

Key figures · 2025

Operating profit
NOK −17,000
▼ −14 %
Equity
NOK −22,000
▼ −330 %

Financial health · 2025

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

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

Who owns GAMLEVEGEN 222 AS?

GAMLEVEGEN 222 AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about GAMLEVEGEN 222 AS

Who owns GAMLEVEGEN 222 AS?

INTERIM MANAGEMENT AS is the largest registered owner, with 60.0%.

Who is the general manager of GAMLEVEGEN 222 AS?

Simen Bjørstad is registered as general manager of GAMLEVEGEN 222 AS.

Where is GAMLEVEGEN 222 AS based?

GAMLEVEGEN 222 AS has its business address in Lillehammer.

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.