BIZTRAC BETA
COMPANY REGISTER PROFILE
917237867 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Other health services

TROND SIGURDSEN AS

Org. no. 917237867 Limited company (AS) Oslo Incorporated 2016 Active
Ownership graph ↗
Equity NOK 2.6m
Incorporated 2016
Share capital NOK 30,000

TROND SIGURDSEN AS is registered as a limited company in Oslo, Oslo with organisation number 917237867. The business is classified under other health services (NACE 86.993). The company was incorporated in 2016. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Investering i aksjer, samt deltakelse i annen virksomhet i Norge.”.

Key figures · 2025

Equity
NOK 2.6m
▼ −13 %
Est. value
NOK 4.0m

Financial health · 2025

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

Who owns TROND SIGURDSEN AS?

TROND SIGURDSEN AS

TROND SIGURDSEN AS has 1 registered shareholder:

All shareholders and roles →

Which companies does TROND SIGURDSEN AS own?

TROND SIGURDSEN AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about TROND SIGURDSEN AS

Who owns TROND SIGURDSEN AS?

TROND SIGURDSEN is the largest registered owner, with 100.0%.

Where is TROND SIGURDSEN AS based?

TROND SIGURDSEN AS has its business address in Oslo.

Property

Business address Gimleveien 24A, 0266 Oslo
Cadastral unit 301-212/417/0/0
Building Stort frittliggende boligbygg på 3 og 4 etg · 20 units

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