BIZTRAC BETA
Marine fishing

BRENNHOLM HOLDING AS

Org. no. 989196316 Limited company (AS) Bergen Incorporated 2005 Active
Ownership graph ↗
Operating profit NOK −44,000
Equity NOK 832,000
Incorporated 2005
Share capital NOK 301,000

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−44k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

BRENNHOLM HOLDING AS is registered as a limited company in Bergen, Vestland with organisation number 989196316. The business is classified under marine fishing (NACE 03.110). The company was incorporated in 2005. Registered share capital is NOK 301,000, divided into 303 shares. The company's stated purpose is: “Næringsvirksomhet i inn- og utland, herunder deltagelse i og/eller investering i andre selskaper, og alt hva dermed er forbundet.”.

Key figures · 2024

Operating profit
NOK −44,000
Equity
NOK 832,000
Est. value
NOK 790,000

Financial health · 2024

Liquidity
0.00
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
27.4%
Good
Equity as a share of total capital

Who owns BRENNHOLM HOLDING AS?

LISBETH BEATE SANDTORV
BRENNHOLM HOLDING AS
· NOK −44,000 profit

BRENNHOLM HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does BRENNHOLM HOLDING AS own?

BRENNHOLM HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about BRENNHOLM HOLDING AS

Who owns BRENNHOLM HOLDING AS?

LISBETH BEATE SANDTORV is the largest registered owner, with 100.0%.

Who is the general manager of BRENNHOLM HOLDING AS?

Lisbeth Beate Sandtorv is registered as general manager of BRENNHOLM HOLDING AS.

Where is BRENNHOLM HOLDING AS based?

BRENNHOLM HOLDING AS has its business address in Hjellestad.

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.