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

BOLIGSAMEIET URANIENBORGVEIEN 29

Org. no. 984048343 Condominium flat owner (ESEK) Oslo Incorporated 2000 Active
Ownership graph ↗
Revenue 2025 NOK 3.5m
Operating profit NOK 3.0m
Equity NOK −3.4m
Incorporated 2000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−3,4 mill kr).

BOLIGSAMEIET URANIENBORGVEIEN 29 is registered as a condominium flat owner in Oslo, Oslo with organisation number 984048343. The business is classified under activities of housing cooperatives (NACE 97.001). The company was incorporated in 2000. The company's stated purpose is: “Å ivareta sameiernes fellesinteresser i drift og administrasjon av eiendommen gnr. 214 bnr. 406 Oslo med fellesanlegg av enhver art.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.5m in revenue and NOK 3.0m in operating profit.

Key figures · 2025

Revenue
NOK 3.5m
▲ +30 %
Operating profit
NOK 3.0m
▲ +208 %
Equity
NOK −3.4m
▲ +43 %
Est. value
NOK 10.3m

Financial health · 2025

Liquidity
2.97
Very good
Current assets ÷ current liabilities
Profitability
396.9%
Very good
Return on total assets
Solidity
-594.2%
Weak
Equity as a share of total capital

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

Who owns BOLIGSAMEIET URANIENBORGVEIEN 29?

No shareholders are registered for BOLIGSAMEIET URANIENBORGVEIEN 29 in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about BOLIGSAMEIET URANIENBORGVEIEN 29

What is the revenue of BOLIGSAMEIET URANIENBORGVEIEN 29?

BOLIGSAMEIET URANIENBORGVEIEN 29 had revenue of NOK 3.5m in 2025.

Where is BOLIGSAMEIET URANIENBORGVEIEN 29 based?

BOLIGSAMEIET URANIENBORGVEIEN 29 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.