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

SAMEIET GLASSVERKET TERRASSE

Org. no. 990386501 Condominium flat owner (ESEK) Oslo Incorporated 1982 Active
Ownership graph ↗
Revenue 2025 NOK 1.4m
Operating profit NOK 351,000
Equity NOK −1.3m
Incorporated 1982

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−1,3 mill kr).
  • Nylig endring 2026-09-23 Adresseendring registrert 2026-09-23.

SAMEIET GLASSVERKET TERRASSE is registered as a condominium flat owner in Oslo, Oslo with organisation number 990386501. The business is classified under activities of housing cooperatives (NACE 97.001). The company was incorporated in 1982. The company's stated purpose is: “Eierseksjonssameie.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.4m in revenue and NOK 351,000 in operating profit.

Former names: ARNE ULSTRUPS VEI 13 - 15 BOLIGSAMEIE, SAMEIET GLASSVERKVEIEN 121 - 127

Key figures · 2025

Revenue
NOK 1.4m
▲ +16 %
Operating profit
NOK 351,000
▼ −28 %
Equity
NOK −1.3m
▲ +14 %
Est. value
NOK 1.5m

Financial health · 2025

Liquidity
8.30
Very good
Current assets ÷ current liabilities
Profitability
54.8%
Very good
Return on total assets
Solidity
-190.2%
Weak
Equity as a share of total capital

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

Who owns SAMEIET GLASSVERKET TERRASSE?

No shareholders are registered for SAMEIET GLASSVERKET TERRASSE in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about SAMEIET GLASSVERKET TERRASSE

What is the revenue of SAMEIET GLASSVERKET TERRASSE?

SAMEIET GLASSVERKET TERRASSE had revenue of NOK 1.4m in 2025.

Where is SAMEIET GLASSVERKET TERRASSE based?

SAMEIET GLASSVERKET TERRASSE has its business address in Oslo.

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.