BIZTRAC BETA
Ventilation installation

STENSEIDE VENTILASJONSSERVICE AS

Org. no. 898546632 Limited company (AS) Askøy Incorporated 2012 Active
Ownership graph ↗
Revenue 2025 NOK 1.5m
Operating profit NOK 47,000
Equity NOK 168,000
Incorporated 2012
Share capital NOK 30,000

STENSEIDE VENTILASJONSSERVICE AS is registered as a limited company in Askøy, Vestland with organisation number 898546632. The business is classified under ventilation installation (NACE 43.223). The company was incorporated in 2012. Registered share capital is NOK 30,000, divided into 200 shares. The company's stated purpose is: “Drive ventilasjonsarbeid og annet som naturlig hører til dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.5m in revenue and NOK 47,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.5m
Operating profit
NOK 47,000
Equity
NOK 168,000
Est. value
NOK 244,000

Financial health · 2025

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

Who owns STENSEIDE VENTILASJONSSERVICE AS?

TROND STENSEIDE
STENSEIDE VENTILASJONSSERVICE AS
NOK 1.5m rev. · NOK 47,000 profit

STENSEIDE VENTILASJONSSERVICE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about STENSEIDE VENTILASJONSSERVICE AS

Who owns STENSEIDE VENTILASJONSSERVICE AS?

TROND STENSEIDE is the largest registered owner, with 100.0%.

What is the revenue of STENSEIDE VENTILASJONSSERVICE AS?

STENSEIDE VENTILASJONSSERVICE AS had revenue of NOK 1.5m in 2025.

Who is the general manager of STENSEIDE VENTILASJONSSERVICE AS?

Trond Stenseide is registered as general manager of STENSEIDE VENTILASJONSSERVICE AS.

Where is STENSEIDE VENTILASJONSSERVICE AS based?

STENSEIDE VENTILASJONSSERVICE AS has its business address in Kleppestø.

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.