BIZTRAC BETA
COMPANY REGISTER PROFILE
932033453 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 02.09.2026
Rental and operating of own or leased real estate

TURNKEY AS

Org. no. 932033453 Limited company (AS) Oslo Incorporated 2023 Active
Ownership graph ↗
Operating profit NOK −146,000
Equity NOK 14.2m
Incorporated 2023
Share capital NOK 2.6m

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−146k kr).

TURNKEY AS is registered as a limited company in Oslo, Oslo with organisation number 932033453. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2023. Registered share capital is NOK 2.6m, divided into 2600000 shares. The company's stated purpose is: “Investere i fast eiendom, enten direkte eller gjennom selskaper, samt drive annen virksomhet som naturlig sammenfaller med dette.”.

Former names: P1 INVEST AS

Key figures · 2025

Operating profit
NOK −146,000
Equity
NOK 14.2m
Est. value
NOK 11.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 TURNKEY AS?

TURNKEY AS has 6 registered shareholders:

All shareholders and roles →

Frequently asked questions about TURNKEY AS

Who owns TURNKEY AS?

AS CLIPPER is the largest registered owner, with 30.0%.

Where is TURNKEY AS based?

TURNKEY AS has its business address in Oslo.

Property

Business address Bolette brygge 1, 0252 Oslo
Cadastral unit 301-210/32/0/0

297 companies are registered at this address.

The address this company is registered at, from the company register and matched against the cadastre. It does not say who owns the property — a company may be a tenant, and the address is often its accountant's. Source: Brønnøysundregistrene and © Kartverket.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 02.09.2026.

Report a problem

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