biztrac. BETA
COMPANY REGISTER PROFILE
988416649 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Rental and operating of own or leased real estate

TROLLÅSVEIEN 34-36 AS

Org. no. 988416649 Limited company (AS) Oslo Incorporated 2005 Active
Revenue 2025 NOK 10.6m
Operating profit NOK 4.8m
Equity NOK 5.3m
Incorporated 2005
Share capital NOK 1.2m

TROLLÅSVEIEN 34-36 AS is registered as a limited company in Oslo, Oslo with organisation number 988416649. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2005. Registered share capital is NOK 1.2m, divided into 1000 shares. The company's stated purpose is: “Investere, alene eller sammen med andre, i fast eiendom og tomter, enten direkte eller indirekte gjennom eie av aksjer eller andeler i selskap eller annen sammenslutning, samt alt annet som står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 10.6m in revenue and NOK 4.8m in operating profit.

Key figures · 2025

Revenue
NOK 10.6m
▲ +12 %
Operating profit
NOK 4.8m
▲ +115 %
Equity
NOK 5.3m
▼ −6 %
Est. value
NOK 10.2m

Financial health · 2025

Liquidity
1.16
Satisfactory
Current assets ÷ current liabilities
Profitability
9.3%
Satisfactory
Return on total assets
Solidity
8.5%
Weak
Equity as a share of total capital

Who owns TROLLÅSVEIEN 34-36 AS?

TROLLÅSVEIEN 34-36 AS
NOK 10.6m rev. · NOK 4.8m profit

TROLLÅSVEIEN 34-36 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TROLLÅSVEIEN 34-36 AS

Who owns TROLLÅSVEIEN 34-36 AS?

GREVESKOGEN NÆRING AS is the largest registered owner, with 100.0%.

What is the revenue of TROLLÅSVEIEN 34-36 AS?

TROLLÅSVEIEN 34-36 AS had revenue of NOK 10.6m in 2025.

Where is TROLLÅSVEIEN 34-36 AS based?

TROLLÅSVEIEN 34-36 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 03.10.2026.

Report a problem

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