BIZTRAC BETA
Other services incidental to land transport n.e.c.

BILBERGING SANDNESSJØEN AS

Org. no. 932926407 Limited company (AS) Alstahaug Incorporated 2024 Active
Ownership graph ↗
Revenue 2024 NOK 2.3m
Operating profit NOK 272,000
Equity NOK 108,000
Incorporated 2024
Share capital NOK 30,000

Signals

1 flags
  • Nylig endring 2026-06-13 Konkurs registrert 2026-06-13.

BILBERGING SANDNESSJØEN AS is registered as a limited company in Alstahaug, Nordland with organisation number 932926407. The business is classified under other services incidental to land transport n.e.c. (NACE 52.219). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Drive bilberging samt transport naturlig tilknyttet dette. Tjeneste tilknyttet landtransport ellers og godstransport på vei.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.3m in revenue and NOK 272,000 in operating profit.

Key figures · 2024

Revenue
NOK 2.3m
Operating profit
NOK 272,000
Equity
NOK 108,000
Est. value
NOK 484,000

Financial health · 2024

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

Who owns BILBERGING SANDNESSJØEN AS?

No shareholders are registered for BILBERGING SANDNESSJØEN AS in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about BILBERGING SANDNESSJØEN AS

What is the revenue of BILBERGING SANDNESSJØEN AS?

BILBERGING SANDNESSJØEN AS had revenue of NOK 2.3m in 2024.

Who is the general manager of BILBERGING SANDNESSJØEN AS?

Bjarne Jørgen Myhre Olsen is registered as general manager of BILBERGING SANDNESSJØEN AS.

Where is BILBERGING SANDNESSJØEN AS based?

BILBERGING SANDNESSJØEN AS has its business address in Sandnessjøen.

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.