BIZTRAC BETA
Business and other management consultancy activities

TROND BJERKE AS

Org. no. 998275547 Limited company (AS) Larvik Incorporated 2012 Active
Ownership graph ↗
Revenue 2025 NOK 73,000
Operating profit NOK 13,000
Equity NOK 43,000
Incorporated 2012
Share capital NOK 30,000

TROND BJERKE AS is registered as a limited company in Larvik, Vestfold with organisation number 998275547. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2012. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Konsulentvirksomhet innenfor data, økonomi, administrasjon og konsulentoppdrag som faller naturlig inn under dette. Kjøp og salg av aksjer og fond samt deltakelse i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 73,000 in revenue and NOK 13,000 in operating profit.

Key figures · 2025

Revenue
NOK 73,000
Operating profit
NOK 13,000
Equity
NOK 43,000
Est. value
NOK 89,000

Financial health · 2025

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

Solidity capped at Weak because equity is below NOK 100,000.

Who owns TROND BJERKE AS?

TROND BJERKE
TROND BJERKE AS
NOK 73,000 rev. · NOK 13,000 profit

TROND BJERKE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TROND BJERKE AS

Who owns TROND BJERKE AS?

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

What is the revenue of TROND BJERKE AS?

TROND BJERKE AS had revenue of NOK 73,000 in 2025.

Who is the general manager of TROND BJERKE AS?

Trond Bjerke is registered as general manager of TROND BJERKE AS.

Where is TROND BJERKE AS based?

TROND BJERKE AS has its business address in Larvik.

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.