BIZTRAC BETA
Rental and operating of own or leased real estate

GRENSEVEIEN 97 BOLIG AS

Org. no. 919291907 Limited company (AS) Oslo Incorporated 2017 Active
Ownership graph ↗
Revenue 2024 NOK 582,000
Operating profit NOK 531,000
Equity NOK 553,000
Incorporated 2017
Share capital NOK 1.1m

GRENSEVEIEN 97 BOLIG AS is registered as a limited company in Oslo, Oslo with organisation number 919291907. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2017. Registered share capital is NOK 1.1m, divided into 111100000 shares. The company's stated purpose is: “Eie, forvalte og utvikle eiendommen gnr. 130, bnr. 219 i Oslo, og alt annet som står i naturlig forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 582,000 in revenue and NOK 531,000 in operating profit.

Key figures · 2024

Revenue
NOK 582,000
Operating profit
NOK 531,000
Equity
NOK 553,000
Est. value
NOK 1.4m

Financial health · 2024

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

Who owns GRENSEVEIEN 97 BOLIG AS?

CANICA AS
GRENSEVEIEN 97 BOLIG AS
NOK 582,000 rev. · NOK 531,000 profit

GRENSEVEIEN 97 BOLIG AS has 11 registered shareholders:

All shareholders and roles →

Which companies does GRENSEVEIEN 97 BOLIG AS own?

GRENSEVEIEN 97 BOLIG AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about GRENSEVEIEN 97 BOLIG AS

Who owns GRENSEVEIEN 97 BOLIG AS?

CANICA AS is the largest registered owner, with 29.7%.

What is the revenue of GRENSEVEIEN 97 BOLIG AS?

GRENSEVEIEN 97 BOLIG AS had revenue of NOK 582,000 in 2024.

Where is GRENSEVEIEN 97 BOLIG AS based?

GRENSEVEIEN 97 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.