BIZTRAC BETA
COMPANY REGISTER PROFILE
919860456 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Other captive investment companies

TREBOR INVESTERINGER AS

Org. no. 919860456 Limited company (AS) Bergen Incorporated 2017 Active
Ownership graph ↗
Equity NOK 11.5m
Incorporated 2017
Share capital NOK 30,000

TREBOR INVESTERINGER AS is registered as a limited company in Bergen, Vestland with organisation number 919860456. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2017. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Investeringsvirksomhet i bred forstand.”.

Key figures · 2025

Equity
NOK 11.5m
Est. value
NOK 29.9m

Financial health · 2025

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

Who owns TREBOR INVESTERINGER AS?

TREBOR INVESTERINGER AS

TREBOR INVESTERINGER AS has 1 registered shareholder:

All shareholders and roles →

Which companies does TREBOR INVESTERINGER AS own?

TREBOR INVESTERINGER AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about TREBOR INVESTERINGER AS

Who owns TREBOR INVESTERINGER AS?

ROBERT LIE OLSEN is the largest registered owner, with 100.0%.

Where is TREBOR INVESTERINGER AS based?

TREBOR INVESTERINGER AS has its business address in Søreidgrend.

Property

Business address Steinsvikvegen 135, 5251 Søreidgrend
Cadastral unit 4601-39/288/0/0
Building Rekkehus · 1 unit

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.