BIZTRAC BETA
Civil engineering activities

DESINTRYGG AS

Org. no. 925321141 Limited company (AS) Bærum Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 985,000
Operating profit NOK −589,000
Equity NOK 534,000
Incorporated 2020
Employees 5
Share capital NOK 638,000

Signals

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

DESINTRYGG AS is registered as a limited company in Bærum, Akershus with organisation number 925321141. The business is classified under civil engineering activities (NACE 71.121). The company was incorporated in 2020 and has 5 registered employees. Registered share capital is NOK 638,000, divided into 19328 shares. The company's stated purpose is: “Bioteknikk og tjenester knyttet til skadebegrensning, oppbygging og sanering av eiendom, og alt som står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 985,000 in revenue and NOK −589,000 in operating profit.

Key figures · 2025

Revenue
NOK 985,000
Operating profit
NOK −589,000
Equity
NOK 534,000
Est. value
NOK 1.3m

Financial health · 2025

Liquidity
4.93
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
79.7%
Very good
Equity as a share of total capital

Who owns DESINTRYGG AS?

LEVELUPKID AS
DESINTRYGG AS
NOK 985,000 rev. · NOK −589,000 profit

DESINTRYGG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about DESINTRYGG AS

Who owns DESINTRYGG AS?

LEVELUPKID AS is the largest registered owner, with 100.0%.

What is the revenue of DESINTRYGG AS?

DESINTRYGG AS had revenue of NOK 985,000 in 2025.

Who is the general manager of DESINTRYGG AS?

Patrick Johannessen Westerby is registered as general manager of DESINTRYGG AS.

Where is DESINTRYGG AS based?

DESINTRYGG AS has its business address in Bekkestua.

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.