BIZTRAC BETA
Repair and maintenance of motor vehicles

PALTEK AS

Org. no. 990717265 Limited company (AS) Sandnes Incorporated 2006 Active
Ownership graph ↗
Revenue 2024 NOK 64.0m
Operating profit NOK 1.7m
Equity NOK 13.9m
Incorporated 2006
Employees 24
Share capital NOK 2.9m

PALTEK AS is registered as a limited company in Sandnes, Rogaland with organisation number 990717265. The business is classified under repair and maintenance of motor vehicles (NACE 95.310). The company was incorporated in 2006 and has 24 registered employees. Registered share capital is NOK 2.9m, divided into 29000 shares. The company's stated purpose is: “Salg, import, montasje av maskiner/utstyr og virksomhet som står i forbindelse med dette, herunder deltakelse i andre selskaper med lignende virksomhet, samt investering i fast eiendom, verdipapirer og andre formuesprosjekter.”. The most recent filed accounts, for the 2024 financial year, show NOK 64.0m in revenue and NOK 1.7m in operating profit.

Key figures · 2024

Revenue
NOK 64.0m
Operating profit
NOK 1.7m
Equity
NOK 13.9m
Est. value
NOK 13.3m

Financial health · 2024

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

Who owns PALTEK AS?

CARIGOSA AS
PALTEK AS
NOK 64.0m rev. · NOK 1.7m profit

PALTEK AS has 1 registered shareholder:

All shareholders and roles →

Which companies does PALTEK AS own?

PALTEK AS holds a stake in 1 company:

See the full ownership structure →

Group structure

PALTEK AS er morselskap for 1 datterselskap:

Frequently asked questions about PALTEK AS

Who owns PALTEK AS?

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

What is the revenue of PALTEK AS?

PALTEK AS had revenue of NOK 64.0m in 2024.

Where is PALTEK AS based?

PALTEK AS has its business address in Sandnes.

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.