BIZTRAC BETA
Other technical consultancy

INSEA QUALITY SERVICES AS

Org. no. 965229531 Limited company (AS) Overhalla Incorporated 1992 Active
Ownership graph ↗
Revenue 2025 NOK 17.6m
Operating profit NOK 2.0m
Equity NOK 123,000
Incorporated 1992
Share capital NOK 113,000

INSEA QUALITY SERVICES AS is registered as a limited company in Overhalla, Trøndelag with organisation number 965229531. The business is classified under other technical consultancy (NACE 71.129). The company was incorporated in 1992. Registered share capital is NOK 113,000, divided into 226 shares. The company's stated purpose is: “Konsulentvirksomhet og produktutvikling innenfor marinteknologi og hva dermed står i forbindelse, samt å interessere seg i andre foretagender.”. The most recent filed accounts, for the 2025 financial year, show NOK 17.6m in revenue and NOK 2.0m in operating profit.

Key figures · 2025

Revenue
NOK 17.6m
Operating profit
NOK 2.0m
Equity
NOK 123,000
Est. value
NOK 10.1m

Financial health · 2025

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

Who owns INSEA QUALITY SERVICES AS?

EGIDIUS SERVICES AS
INSEA QUALITY SERVICES AS
NOK 17.6m rev. · NOK 2.0m profit

INSEA QUALITY SERVICES AS has 4 registered shareholders:

All shareholders and roles →

Frequently asked questions about INSEA QUALITY SERVICES AS

Who owns INSEA QUALITY SERVICES AS?

EGIDIUS SERVICES AS is the largest registered owner, with 33.6%.

What is the revenue of INSEA QUALITY SERVICES AS?

INSEA QUALITY SERVICES AS had revenue of NOK 17.6m in 2025.

Who is the general manager of INSEA QUALITY SERVICES AS?

Jens Koch is registered as general manager of INSEA QUALITY SERVICES AS.

Where is INSEA QUALITY SERVICES AS based?

INSEA QUALITY SERVICES AS has its business address in Skage I Namdalen.

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.