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

GRENSEN 17 AS

Org. no. 921129548 Limited company (AS) Oslo Incorporated 2018 Active
Revenue 2025 NOK 27.9m
Operating profit NOK 25.4m
Equity NOK 295.3m
Incorporated 2018
Share capital NOK 300,000

Signals

1 flags
  • Nylig endring 2026-07-01 Adresseendring registrert 2026-07-01.

GRENSEN 17 AS is registered as a limited company in Oslo, Oslo with organisation number 921129548. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2018. Registered share capital is NOK 300,000, divided into 30000 shares. The company's stated purpose is: “Eie fast eiendom og investere i fast eiendom eller selskaper som eier fast eiendom, samt all annen virksomhet som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 27.9m in revenue and NOK 25.4m in operating profit.

Key figures · 2025

Revenue
NOK 27.9m
▼ −4 %
Operating profit
NOK 25.4m
▲ +2 %
Equity
NOK 295.3m
▲ +2 %
Est. value
NOK 265.6m

Financial health · 2025

Liquidity
1.64
Good
Current assets ÷ current liabilities
Profitability
8.0%
Satisfactory
Return on total assets
Solidity
79.8%
Very good
Equity as a share of total capital

Who owns GRENSEN 17 AS?

GRENSEN 17 AS
NOK 27.9m rev. · NOK 25.4m profit

GRENSEN 17 AS has 1 registered shareholder:

All shareholders and roles →

Group structure

GRENSEN 17 AS er morselskap for 10 datterselskaper:

Frequently asked questions about GRENSEN 17 AS

Who owns GRENSEN 17 AS?

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

What is the revenue of GRENSEN 17 AS?

GRENSEN 17 AS had revenue of NOK 27.9m in 2025.

Where is GRENSEN 17 AS based?

GRENSEN 17 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.