BIZTRAC BETA
Repair and maintenance of machinery

SAXE PLAST TEKNIKK AS

Org. no. 924662042 Limited company (AS) Drammen Incorporated 2020 Active
Ownership graph ↗
Revenue 2024 NOK 22.8m
Operating profit NOK 418,000
Equity NOK 832,000
Incorporated 2020
Share capital NOK 100,000

SAXE PLAST TEKNIKK AS is registered as a limited company in Drammen, Buskerud with organisation number 924662042. The business is classified under repair and maintenance of machinery (NACE 33.120). The company was incorporated in 2020. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Agenturhandel, salg av industrielle produkter og tjenester, konsulent og servicetjenester.”. The most recent filed accounts, for the 2024 financial year, show NOK 22.8m in revenue and NOK 418,000 in operating profit.

Key figures · 2024

Revenue
NOK 22.8m
Operating profit
NOK 418,000
Equity
NOK 832,000
Est. value
NOK 1.9m

Financial health · 2024

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

Who owns SAXE PLAST TEKNIKK AS?

P. SAXE NIELSEN APS
SAXE PLAST TEKNIKK AS
NOK 22.8m rev. · NOK 418,000 profit

SAXE PLAST TEKNIKK AS has 2 registered shareholders:

All shareholders and roles →

Group structure

SAXE PLAST TEKNIKK AS er morselskap for 1 datterselskap:

Frequently asked questions about SAXE PLAST TEKNIKK AS

Who owns SAXE PLAST TEKNIKK AS?

P. SAXE NIELSEN APS is the largest registered owner, with 90.0%.

What is the revenue of SAXE PLAST TEKNIKK AS?

SAXE PLAST TEKNIKK AS had revenue of NOK 22.8m in 2024.

Who is the general manager of SAXE PLAST TEKNIKK AS?

Ulrik Gert Nielsen is registered as general manager of SAXE PLAST TEKNIKK AS.

Where is SAXE PLAST TEKNIKK AS based?

SAXE PLAST TEKNIKK AS has its business address in Mjøndalen.

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.