BIZTRAC BETA
Business and other management consultancy activities

BT INVESTERING AS

Org. no. 917984352 Limited company (AS) Stavanger Incorporated 2016 Active
Ownership graph ↗
Revenue 2024 NOK 1.8m
Operating profit NOK 99,000
Equity NOK 6.1m
Incorporated 2016
Share capital NOK 30,000

BT INVESTERING AS is registered as a limited company in Stavanger, Rogaland with organisation number 917984352. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2016. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Virksomhet innenfor utvikling og investering i andre selskaper og alt som står i forbindelse med de forannevnte virksomheter. Selskapet skal også drive med bedriftsrådgivning og utleie av arbeidskraft.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.8m in revenue and NOK 99,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.8m
Operating profit
NOK 99,000
Equity
NOK 6.1m
Est. value
NOK 3.9m

Financial health · 2024

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

Who owns BT INVESTERING AS?

GUSTAV TVEIT
BT INVESTERING AS
NOK 1.8m rev. · NOK 99,000 profit

BT INVESTERING AS has 2 registered shareholders:

All shareholders and roles →

Which companies does BT INVESTERING AS own?

BT INVESTERING AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about BT INVESTERING AS

Who owns BT INVESTERING AS?

GUSTAV TVEIT is the largest registered owner, with 50.0%.

What is the revenue of BT INVESTERING AS?

BT INVESTERING AS had revenue of NOK 1.8m in 2024.

Where is BT INVESTERING AS based?

BT INVESTERING AS has its business address in Stavanger.

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

Report a problem

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