biztrac. BETA
COMPANY REGISTER PROFILE
935787084 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Retail sale of motor vehicles

BALORENTZEN HOLDING AS

Org. no. 935787084 Limited company (AS) Harstad Incorporated 2025 Active
Operating profit NOK −7,000
Equity NOK 17,000
Incorporated 2025
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−7k kr).

BALORENTZEN HOLDING AS is registered as a limited company in Harstad, Troms with organisation number 935787084. The business is classified under retail sale of motor vehicles (NACE 47.810). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Å eie aksjer eller eierandeler i andre selskaper, samt å foreta andre investeringer og forvalte disse investeringene.”.

Key figures · 2025

Operating profit
NOK −7,000
Equity
NOK 17,000
Est. value
NOK 21,000

Financial health · 2025

Liquidity
–
Not available
Current assets ÷ current liabilities
Profitability
–
Not available
Return on total assets
Solidity
0.9%
Weak
Equity as a share of total capital

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

Who owns BALORENTZEN HOLDING AS?

BALORENTZEN HOLDING AS
· NOK −7,000 profit

BALORENTZEN HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does BALORENTZEN HOLDING AS own?

BALORENTZEN HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about BALORENTZEN HOLDING AS

Who owns BALORENTZEN HOLDING AS?

Bjørn-Are Lorentzen is the largest registered owner, with 100.0%.

Who is the general manager of BALORENTZEN HOLDING AS?

Bjørn-Are Lorentzen is registered as general manager of BALORENTZEN HOLDING AS.

Where is BALORENTZEN HOLDING AS based?

BALORENTZEN HOLDING AS has its business address in Harstad.

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

Report a problem

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