BIZTRAC BETA
COMPANY REGISTER PROFILE
935159318 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Buying and selling of own real estate

SAGA PARK AS

Org. no. 935159318 Limited company (AS) Trondheim Incorporated 2025 Active
Ownership graph ↗
Operating profit NOK −12,000
Equity NOK 11.8m
Incorporated 2025
Share capital NOK 2.0m

Signals

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

SAGA PARK AS is registered as a limited company in Trondheim, Trøndelag with organisation number 935159318. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2025. Registered share capital is NOK 2.0m, divided into 20000 shares. The company's stated purpose is: “Kjøp, salg, utvikling og drift av fast eiendom, samt det som naturlig hører inn under dette.”.

Key figures · 2025

Operating profit
NOK −12,000
Equity
NOK 11.8m
Est. value
NOK 10.8m

Financial health · 2025

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

Who owns SAGA PARK AS?

SAGA PARK AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about SAGA PARK AS

Who owns SAGA PARK AS?

BYGGTEKNIKK UTVIKLING AS is the largest registered owner, with 50.0%.

Where is SAGA PARK AS based?

SAGA PARK AS has its business address in Trondheim.

Property

Business address c/o Byggteknikk Utvikling AS Bassengbakken 4, 7042 Trondheim
Cadastral unit 5001-410/589/0/0
Building Annen kontorbygning · 13 units

53 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.