BIZTRAC BETA
Combined facilities support activities

PRO-TECK AS

Org. no. 988921114 Limited company (AS) Frosta Incorporated 2005 Active
Ownership graph ↗
Revenue 2024 NOK 59,000
Operating profit NOK 14,000
Equity NOK 327,000
Incorporated 2005
Share capital NOK 50,000

PRO-TECK AS is registered as a limited company in Frosta, Trøndelag with organisation number 988921114. The business is classified under combined facilities support activities (NACE 81.100). The company was incorporated in 2005. Registered share capital is NOK 50,000, divided into 50 shares. The company's stated purpose is: “Handel med vaktmester og renholdstjenester, oppføring og vedlikehold bygg, verksted og lagersystemer, maskiner og utstyr og alt som derved står i forbindelse med, samt delta i andre foretagende.”. The most recent filed accounts, for the 2024 financial year, show NOK 59,000 in revenue and NOK 14,000 in operating profit.

Key figures · 2024

Revenue
NOK 59,000
Operating profit
NOK 14,000
Equity
NOK 327,000
Est. value
NOK 215,000

Financial health · 2024

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

Who owns PRO-TECK AS?

JON ANDOR HOVDAL
PRO-TECK AS
NOK 59,000 rev. · NOK 14,000 profit

PRO-TECK AS has 1 registered shareholder:

All shareholders and roles →

Which companies does PRO-TECK AS own?

PRO-TECK AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about PRO-TECK AS

Who owns PRO-TECK AS?

JON ANDOR HOVDAL is the largest registered owner, with 100.0%.

What is the revenue of PRO-TECK AS?

PRO-TECK AS had revenue of NOK 59,000 in 2024.

Who is the general manager of PRO-TECK AS?

Jon Andor Hovdal is registered as general manager of PRO-TECK AS.

Where is PRO-TECK AS based?

PRO-TECK AS has its business address in Frosta.

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.