biztrac. BETA
COMPANY REGISTER PROFILE
933249352 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Wholesale of other machinery and equipment

WITRE AS

Org. no. 933249352 Limited company (AS) Halden Incorporated 1983 Active
Ownership graph ↗
Revenue 2025 NOK 114.4m
Operating profit NOK 5.8m
Equity NOK 43.3m
Incorporated 1983
Employees 5
Share capital NOK 1.0m

WITRE AS is registered as a limited company in Halden, Østfold with organisation number 933249352. The business is classified under wholesale of other machinery and equipment (NACE 46.640). The company was incorporated in 1983 and has 5 registered employees. Registered share capital is NOK 1.0m, divided into 1000 shares. The company's stated purpose is: “Import- og handelsvirksomhet, derunder postordre- virksomhet samt hva hermed står i forbindelse. Selskapet kan ved innskudd eller på annen måte gjøre seg interessert i andre foretagender.”. The most recent filed accounts, for the 2025 financial year, show NOK 114.4m in revenue and NOK 5.8m in operating profit.

Key figures · 2025

Revenue
NOK 114.4m
▲ +2 %
Operating profit
NOK 5.8m
▲ +4 %
Equity
NOK 43.3m
▲ +12 %
Est. value
NOK 49.3m

Financial health · 2025

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

Who owns WITRE AS?

WITRE AB SE
WITRE AS
NOK 114.4m rev. · NOK 5.8m profit

WITRE AS has 1 registered shareholder:

  • WITRE AB 100.0%
All shareholders and roles →

Frequently asked questions about WITRE AS

Who owns WITRE AS?

WITRE AB is the largest registered owner, with 100.0%.

What is the revenue of WITRE AS?

WITRE AS had revenue of NOK 114.4m in 2025.

Who is the general manager of WITRE AS?

Espen Olav Sætre is registered as general manager of WITRE AS.

Where is WITRE AS based?

WITRE AS has its business address in Halden.

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.