BIZTRAC BETA
Other technical consultancy

JAD ENGINEERING AS

Org. no. 919401362 Limited company (AS) Indre Østfold Incorporated 2017 Active
Ownership graph ↗
Revenue 2025 NOK 1.7m
Operating profit NOK 278,000
Equity NOK 52,000
Incorporated 2017
Share capital NOK 30,000

JAD ENGINEERING AS is registered as a limited company in Indre Østfold, Østfold with organisation number 919401362. The business is classified under other technical consultancy (NACE 71.129). The company was incorporated in 2017. Registered share capital is NOK 30,000, divided into 300000 shares. The company's stated purpose is: “Engineering og commissioning av automasjonsanlegg for skip, offshore on industri.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.7m in revenue and NOK 278,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.7m
Operating profit
NOK 278,000
Equity
NOK 52,000
Est. value
NOK 1.4m

Financial health · 2025

Liquidity
1.10
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
9.8%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns JAD ENGINEERING AS?

JAD INVEST AS
JAD ENGINEERING AS
NOK 1.7m rev. · NOK 278,000 profit

JAD ENGINEERING AS has 1 registered shareholder:

All shareholders and roles →

Group structure

JAD ENGINEERING AS er morselskap for 1 datterselskap:

Frequently asked questions about JAD ENGINEERING AS

Who owns JAD ENGINEERING AS?

JAD INVEST AS is the largest registered owner, with 100.0%.

What is the revenue of JAD ENGINEERING AS?

JAD ENGINEERING AS had revenue of NOK 1.7m in 2025.

Who is the general manager of JAD ENGINEERING AS?

Johnny Arve Drivenes is registered as general manager of JAD ENGINEERING AS.

Where is JAD ENGINEERING AS based?

JAD ENGINEERING AS has its business address in Spydeberg.

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.