biztrac. BETA
COMPANY REGISTER PROFILE
983259286 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Other real estate activities on a fee or contract basis

YES ENGINEERING AS

Org. no. 983259286 Limited company (AS) Bergen Incorporated 2001 Active
Ownership graph ↗
Revenue 2025 NOK 279,000
Operating profit NOK 185,000
Equity NOK 3.1m
Incorporated 2001
Share capital NOK 100,000

YES ENGINEERING AS is registered as a limited company in Bergen, Vestland with organisation number 983259286. The business is classified under other real estate activities on a fee or contract basis (NACE 68.320). The company was incorporated in 2001. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Eiendomsforvaltning og utvikling. Rådgivende ingeniørvirksomhet. Design og produksjon av effektive transportløsninger.”. The most recent filed accounts, for the 2025 financial year, show NOK 279,000 in revenue and NOK 185,000 in operating profit.

Former names: HÅKONSGATEN 17 AS

Key figures · 2025

Revenue
NOK 279,000
▲ +8232 %
Operating profit
NOK 185,000
▲ +165 %
Equity
NOK 3.1m
▲ +3 %
Est. value
NOK 2.5m

Financial health · 2025

Liquidity
3.52
Very good
Current assets ÷ current liabilities
Profitability
6.1%
Satisfactory
Return on total assets
Solidity
98.2%
Very good
Equity as a share of total capital

Who owns YES ENGINEERING AS?

YES ENGINEERING AS
NOK 279,000 rev. · NOK 185,000 profit

YES ENGINEERING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about YES ENGINEERING AS

Who owns YES ENGINEERING AS?

Hans Magne Øpstad is the largest registered owner, with 100.0%.

What is the revenue of YES ENGINEERING AS?

YES ENGINEERING AS had revenue of NOK 279,000 in 2025.

Where is YES ENGINEERING AS based?

YES ENGINEERING AS has its business address in Rådal.

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.