BIZTRAC BETA
Other technical consultancy

STABILATOR AS

Org. no. 925231584 Limited company (AS) Drammen Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 2.7m
Operating profit NOK 171,000
Equity NOK 115,000
Incorporated 2020
Share capital NOK 30,000

STABILATOR AS is registered as a limited company in Drammen, Buskerud with organisation number 925231584. The business is classified under other technical consultancy (NACE 71.129). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Fremstilling/salg av konsulenttjenester, prosjektledning og andre produkter som naturlig faller sammen med dette, herunder å delta i andre selskaper med lignende virksomhet, kjøp og salg av aksjer, eller på annen måte gjøre seg interessert i andre foretak.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.7m in revenue and NOK 171,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.7m
Operating profit
NOK 171,000
Equity
NOK 115,000
Est. value
NOK 914,000

Financial health · 2025

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

Who owns STABILATOR AS?

PATRIK ALEXANDER HALLENBORG
STABILATOR AS
NOK 2.7m rev. · NOK 171,000 profit

STABILATOR AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about STABILATOR AS

Who owns STABILATOR AS?

PATRIK ALEXANDER HALLENBORG is the largest registered owner, with 100.0%.

What is the revenue of STABILATOR AS?

STABILATOR AS had revenue of NOK 2.7m in 2025.

Who is the general manager of STABILATOR AS?

Patrik Alexander Hallenborg is registered as general manager of STABILATOR AS.

Where is STABILATOR AS based?

STABILATOR AS has its business address in Drammen.

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.