BIZTRAC BETA
All other professional, scientific and technical activities n.e.c.

ARITEC AS

Org. no. 976187873 Limited company (AS) Lillesand Incorporated 1995 Active
Ownership graph ↗
Revenue 2025 NOK 3,000
Operating profit NOK −398,000
Equity NOK 7.4m
Incorporated 1995
Share capital NOK 100,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−398k kr).

ARITEC AS is registered as a limited company in Lillesand, Agder with organisation number 976187873. The business is classified under all other professional, scientific and technical activities n.e.c. (NACE 74.990). The company was incorporated in 1995. Registered share capital is NOK 100,000, divided into 50 shares. The company's stated purpose is: “Å drive med konsulent- og ingeniørtjenester rettet mot offentlig virksomhet, mekanisk industri og offshorenæringen, samt investere i annen virksomhet som selskapet finner formålstjenlig.”. The most recent filed accounts, for the 2025 financial year, show NOK 3,000 in revenue and NOK −398,000 in operating profit.

Key figures · 2025

Revenue
NOK 3,000
Operating profit
NOK −398,000
Equity
NOK 7.4m
Est. value
NOK 3.6m

Financial health · 2025

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

Who owns ARITEC AS?

ARILD SÆBØ
ARITEC AS
NOK 3,000 rev. · NOK −398,000 profit

ARITEC AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about ARITEC AS

Who owns ARITEC AS?

ARILD SÆBØ is the largest registered owner, with 60.0%.

What is the revenue of ARITEC AS?

ARITEC AS had revenue of NOK 3,000 in 2025.

Who is the general manager of ARITEC AS?

Wenche Wehus is registered as general manager of ARITEC AS.

Where is ARITEC AS based?

ARITEC AS has its business address in Lillesand.

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.