BIZTRAC BETA
Rental and operating of own or leased real estate

STORGATA 178 AS

Org. no. 918616276 Limited company (AS) Lillehammer Incorporated 2016 Active
Ownership graph ↗
Revenue 2024 NOK 4.5m
Operating profit NOK 2.5m
Equity NOK 11.3m
Incorporated 2016
Share capital NOK 1.4m

Signals

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

STORGATA 178 AS is registered as a limited company in Lillehammer, Innlandet with organisation number 918616276. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2016. Registered share capital is NOK 1.4m, divided into 1419182 shares. The company's stated purpose is: “Eie og forestå drift av forretningseiendommer samt tilknyttet næringsvirksomhet og annen virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 4.5m in revenue and NOK 2.5m in operating profit.

Key figures · 2024

Revenue
NOK 4.5m
Operating profit
NOK 2.5m
Equity
NOK 11.3m
Est. value
NOK 12.5m

Financial health · 2024

Liquidity
0.00
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
36.3%
Good
Equity as a share of total capital

Who owns STORGATA 178 AS?

GAUS AS
STORGATA 178 AS
NOK 4.5m rev. · NOK 2.5m profit

STORGATA 178 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about STORGATA 178 AS

Who owns STORGATA 178 AS?

GAUS AS is the largest registered owner, with 100.0%.

What is the revenue of STORGATA 178 AS?

STORGATA 178 AS had revenue of NOK 4.5m in 2024.

Who is the general manager of STORGATA 178 AS?

Åge Erling Melbø is registered as general manager of STORGATA 178 AS.

Where is STORGATA 178 AS based?

STORGATA 178 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 15.06.2026.

Report a problem

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