BIZTRAC BETA
All other professional, scientific and technical activities n.e.c.

BTE CONSULT AS

Org. no. 812893882 Limited company (AS) Øvre Eiker Incorporated 2013 Active
Ownership graph ↗
Revenue 2025 NOK 2.0m
Operating profit NOK 745,000
Equity NOK 3.2m
Incorporated 2013
Share capital NOK 30,000

BTE CONSULT AS is registered as a limited company in Øvre Eiker, Buskerud with organisation number 812893882. The business is classified under all other professional, scientific and technical activities n.e.c. (NACE 74.990). The company was incorporated in 2013. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Tilby konsulenttjenester innenfor bygg-forvaltning, rådgivning og taksering. I tillegg bygg-virksomhet, herunder deltagelse i andre selskaper. Selskapets formål skal også være å gi gaver til ideell virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.0m in revenue and NOK 745,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.0m
Operating profit
NOK 745,000
Equity
NOK 3.2m
Est. value
NOK 4.6m

Financial health · 2025

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

Who owns BTE CONSULT AS?

TROND ERIKSEN
BTE CONSULT AS
NOK 2.0m rev. · NOK 745,000 profit

BTE CONSULT AS has 1 registered shareholder:

All shareholders and roles →

Which companies does BTE CONSULT AS own?

BTE CONSULT AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about BTE CONSULT AS

Who owns BTE CONSULT AS?

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

What is the revenue of BTE CONSULT AS?

BTE CONSULT AS had revenue of NOK 2.0m in 2025.

Where is BTE CONSULT AS based?

BTE CONSULT AS has its business address in Vestfossen.

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.