biztrac. BETA
COMPANY REGISTER PROFILE
935151783 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Uoppgitt

HALLSETH HOLDING AS

Org. no. 935151783 Limited company (AS) Bergen Incorporated 2025 Active
Ownership graph ↗
Operating profit NOK −17,000
Equity NOK 13,000
Incorporated 2025
Share capital NOK 30,000

Signals

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

HALLSETH HOLDING AS is registered as a limited company in Bergen, Vestland with organisation number 935151783. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Eie aksjer i andre selskaper, samt drive investering og forvaltning tilknyttet dette. Selskapet kan også drive med annen virksomhet som står i forbindelse med dette formålet.”.

Key figures · 2025

Operating profit
NOK −17,000
Equity
NOK 13,000
Est. value
NOK 15,000

Financial health · 2025

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

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

Who owns HALLSETH HOLDING AS?

HALLSETH HOLDING AS
· NOK −17,000 profit

HALLSETH HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does HALLSETH HOLDING AS own?

HALLSETH HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about HALLSETH HOLDING AS

Who owns HALLSETH HOLDING AS?

Daniel Hallseth is the largest registered owner, with 100.0%.

Who is the general manager of HALLSETH HOLDING AS?

Daniel Hallseth is registered as general manager of HALLSETH HOLDING AS.

Where is HALLSETH HOLDING AS based?

HALLSETH HOLDING AS has its business address in Laksevåg.

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.