BIZTRAC BETA
Other cleaning activities

BERGEN SKADEDYRKONTROLL AS

Org. no. 928758982 Limited company (AS) Bergen Incorporated 2022 Active
Ownership graph ↗
Revenue 2024 NOK 1.6m
Operating profit NOK −948,000
Equity NOK −954,000
Incorporated 2022
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−954k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−948k kr).

BERGEN SKADEDYRKONTROLL AS is registered as a limited company in Bergen, Vestland with organisation number 928758982. The business is classified under other cleaning activities (NACE 81.230). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 200 shares. The company's stated purpose is: “Drive skadedyrbekjempelse, samt annen virksomhet som naturlig faller innunder dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.6m in revenue and NOK −948,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.6m
Operating profit
NOK −948,000
Equity
NOK −954,000

Financial health · 2024

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

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

Who owns BERGEN SKADEDYRKONTROLL AS?

HAWK AS
BERGEN SKADEDYRKONTROLL AS
NOK 1.6m rev. · NOK −948,000 profit

BERGEN SKADEDYRKONTROLL AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about BERGEN SKADEDYRKONTROLL AS

Who owns BERGEN SKADEDYRKONTROLL AS?

HAWK AS is the largest registered owner, with 91.0%.

What is the revenue of BERGEN SKADEDYRKONTROLL AS?

BERGEN SKADEDYRKONTROLL AS had revenue of NOK 1.6m in 2024.

Where is BERGEN SKADEDYRKONTROLL AS based?

BERGEN SKADEDYRKONTROLL AS has its business address in Nyborg.

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.