BIZTRAC BETA
Other technical consultancy

SEANOVENT ENGINEERING AS

Org. no. 926417010 Limited company (AS) Oslo Incorporated 2021 Active
Ownership graph ↗
Revenue 2024 NOK 5.7m
Operating profit NOK 55,000
Equity NOK 301,000
Incorporated 2021
Share capital NOK 30,000

SEANOVENT ENGINEERING AS is registered as a limited company in Oslo, Oslo with organisation number 926417010. The business is classified under other technical consultancy (NACE 71.129). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Konsulenttjenester, studier og/eller utvikling av produkter og systemer innen energisektoren med spesiell kompetanse innen prosess anlegg og strukturer til havs eller under vann.”. The most recent filed accounts, for the 2024 financial year, show NOK 5.7m in revenue and NOK 55,000 in operating profit.

Key figures · 2024

Revenue
NOK 5.7m
Operating profit
NOK 55,000
Equity
NOK 301,000
Est. value
NOK 520,000

Financial health · 2024

Liquidity
1.23
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
18.7%
Good
Equity as a share of total capital

Who owns SEANOVENT ENGINEERING AS?

KÅRE YRJAN TOLO
SEANOVENT ENGINEERING AS
NOK 5.7m rev. · NOK 55,000 profit

SEANOVENT ENGINEERING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SEANOVENT ENGINEERING AS

Who owns SEANOVENT ENGINEERING AS?

KÅRE YRJAN TOLO is the largest registered owner, with 100.0%.

What is the revenue of SEANOVENT ENGINEERING AS?

SEANOVENT ENGINEERING AS had revenue of NOK 5.7m in 2024.

Who is the general manager of SEANOVENT ENGINEERING AS?

Kåre Yrjan Tolo is registered as general manager of SEANOVENT ENGINEERING AS.

Where is SEANOVENT ENGINEERING AS based?

SEANOVENT ENGINEERING AS has its business address in Oslo.

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.