BIZTRAC BETA
Demolition

RIVINGSSPESIALISTENE AS

Org. no. 929483944 Limited company (AS) Bodø Incorporated 2022 Active
Ownership graph ↗
Revenue 2023 NOK 0
Operating profit NOK 0
Equity NOK 0
Incorporated 2022
Share capital NOK 30,000

Signals

2 flags
  • Utdatert regnskap Siste registrerte regnskap er fra 2023.
  • Nylig endring 2026-06-23 Under avvikling registrert 2026-06-23.

RIVINGSSPESIALISTENE AS is registered as a limited company in Bodø, Nordland with organisation number 929483944. The business is classified under demolition (NACE 43.110). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 2000 shares. The company's stated purpose is: “Rivings, renoverings og bygningstjenester og annen beslektet virksomhet.”. The most recent filed accounts, for the 2023 financial year, show NOK 0 in revenue and NOK 0 in operating profit.

Key figures · 2023

Revenue
NOK 0
Operating profit
NOK 0
Equity
NOK 0

Financial health · 2023

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

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

Who owns RIVINGSSPESIALISTENE AS?

Blazej Kacper Pszczola
RIVINGSSPESIALISTENE AS
NOK 0 rev. · NOK 0 profit

RIVINGSSPESIALISTENE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about RIVINGSSPESIALISTENE AS

Who owns RIVINGSSPESIALISTENE AS?

Blazej Kacper Pszczola is the largest registered owner, with 100.0%.

What is the revenue of RIVINGSSPESIALISTENE AS?

RIVINGSSPESIALISTENE AS had revenue of NOK 0 in 2023.

Who is the general manager of RIVINGSSPESIALISTENE AS?

Blazej Kacper Pszczola is registered as general manager of RIVINGSSPESIALISTENE AS.

Where is RIVINGSSPESIALISTENE AS based?

RIVINGSSPESIALISTENE AS has its business address in Bodø.

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.