biztrac. BETA
COMPANY REGISTER PROFILE
983224903 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Activities of housing cooperatives

GRØNSTADGATEN GARASJELAG SA

Org. no. 983224903 Co-operation (SA) Lillehammer Incorporated 2001 Active
Revenue 2025 NOK 67,000
Operating profit NOK 30,000
Equity NOK −70,000
Incorporated 2001

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−70k kr).

GRØNSTADGATEN GARASJELAG SA is registered as a co-operation in Lillehammer, Innlandet with organisation number 983224903. The business is classified under activities of housing cooperatives (NACE 97.001). The company was incorporated in 2001. The company's stated purpose is: “Å gi andelseierne bruksrett til sin egen garasje i lagets eiendom (garasjerett) og å drive virksomhet som står i sammenheng med denne.”. The most recent filed accounts, for the 2025 financial year, show NOK 67,000 in revenue and NOK 30,000 in operating profit.

Former names: GRØNSTADGATEN GARASJELAG, GRØNSTADGATEN GARASJELAG BA

Key figures · 2025

Revenue
NOK 67,000
▲ +10 %
Operating profit
NOK 30,000
▲ +24 %
Equity
NOK −70,000
▲ +25 %

Financial health · 2025

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

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

Who owns GRØNSTADGATEN GARASJELAG SA?

No shareholders are registered for GRØNSTADGATEN GARASJELAG SA in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about GRØNSTADGATEN GARASJELAG SA

What is the revenue of GRØNSTADGATEN GARASJELAG SA?

GRØNSTADGATEN GARASJELAG SA had revenue of NOK 67,000 in 2025.

Where is GRØNSTADGATEN GARASJELAG SA based?

GRØNSTADGATEN GARASJELAG SA 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.