BIZTRAC BETA
COMPANY REGISTER PROFILE
996953718 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 15.06.2026
Rental and operating of own or leased real estate

TRONDHEIMSVEIEN 139 OSLO AS

Org. no. 996953718 Limited company (AS) Oslo Incorporated 2011 Active
Ownership graph ↗
Operating profit NOK −100,000
Equity NOK 1.5m
Incorporated 2011
Share capital NOK 100,000

Signals

2 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−100k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

TRONDHEIMSVEIEN 139 OSLO AS is registered as a limited company in Oslo, Oslo with organisation number 996953718. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2011. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Investering i fast eiendom, herunder utleie, drift, kjøp og salg, samt investering i aksjer og andre verdipapirer, herunder aktiv deltagelse i andre selskaper. I tillegg kommer annen nærliggende virksomhet.”.

Key figures · 2025

Operating profit
NOK −100,000
Equity
NOK 1.5m
Est. value
NOK 1.1m

Financial health · 2025

Liquidity
Not available
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
100.0%
Very good
Equity as a share of total capital

Who owns TRONDHEIMSVEIEN 139 OSLO AS?

RAGDE EIENDOM AS
TRONDHEIMSVEIEN 139 OSLO AS
· NOK −100,000 profit

TRONDHEIMSVEIEN 139 OSLO AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TRONDHEIMSVEIEN 139 OSLO AS

Who owns TRONDHEIMSVEIEN 139 OSLO AS?

RAGDE EIENDOM AS is the largest registered owner, with 100.0%.

Where is TRONDHEIMSVEIEN 139 OSLO AS based?

TRONDHEIMSVEIEN 139 OSLO 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.