BIZTRAC BETA
Rental and operating of own or leased real estate

GLASSVERKET BOLIG AS

Org. no. 918308121 Limited company (AS) Oslo Incorporated 2016 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −1.3m
Equity NOK −4.7m
Incorporated 2016
Share capital NOK 31,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−4,7 mill kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−1,3 mill kr).

GLASSVERKET BOLIG AS is registered as a limited company in Oslo, Oslo with organisation number 918308121. 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 31,000, divided into 2840 shares. The company's stated purpose is: “Selskapets formål er å eie og utvikle eiendommen Glassverket 2 (gnr. 1, bnr. 1241/3761) i Moss kommune, samt hva som står i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −1.3m in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −1.3m
Equity
NOK −4.7m

Financial health · 2024

Liquidity
1.73
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-290.3%
Weak
Equity as a share of total capital

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

Who owns GLASSVERKET BOLIG AS?

ALTEA AS
GLASSVERKET BOLIG AS
NOK 0 rev. · NOK −1.3m profit

GLASSVERKET BOLIG AS has 9 registered shareholders:

All shareholders and roles →

Frequently asked questions about GLASSVERKET BOLIG AS

Who owns GLASSVERKET BOLIG AS?

ALTEA AS is the largest registered owner, with 25.0%.

What is the revenue of GLASSVERKET BOLIG AS?

GLASSVERKET BOLIG AS had revenue of NOK 0 in 2024.

Where is GLASSVERKET BOLIG AS based?

GLASSVERKET BOLIG AS has its business address in Oslo.

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.