biztrac. BETA
COMPANY REGISTER PROFILE
986543635 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Combined facilities support activities

PROSERVE AS

Org. no. 986543635 Limited company (AS) Halden Incorporated 2004 Active
Ownership graph ↗
Revenue 2025 NOK 12.3m
Operating profit NOK 557,000
Equity NOK 2.2m
Incorporated 2004
Employees 13
Share capital NOK 100,000

PROSERVE AS is registered as a limited company in Halden, Østfold with organisation number 986543635. The business is classified under combined facilities support activities (NACE 81.100). The company was incorporated in 2004 and has 13 registered employees. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Vedlikeholdstjenester samt personal-, bedrifts-, og organisasjonsforvaltning og utvikling, samt kjøp, salg og utleie av utstyr og fast eiendom.”. The most recent filed accounts, for the 2025 financial year, show NOK 12.3m in revenue and NOK 557,000 in operating profit.

Key figures · 2025

Revenue
NOK 12.3m
▲ +34 %
Operating profit
NOK 557,000
▲ +162 %
Equity
NOK 2.2m
▲ +31 %
Est. value
NOK 2.9m

Financial health · 2025

Liquidity
1.99
Good
Current assets ÷ current liabilities
Profitability
14.2%
Good
Return on total assets
Solidity
50.4%
Very good
Equity as a share of total capital

Who owns PROSERVE AS?

PROSERVE AS
NOK 12.3m rev. · NOK 557,000 profit

PROSERVE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about PROSERVE AS

Who owns PROSERVE AS?

PROSERVE HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of PROSERVE AS?

PROSERVE AS had revenue of NOK 12.3m in 2025.

Who is the general manager of PROSERVE AS?

Thor Erling Thorsen is registered as general manager of PROSERVE AS.

Where is PROSERVE AS based?

PROSERVE AS has its business address in Tistedal.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.