BIZTRAC BETA
COMPANY REGISTER PROFILE
921158718 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 15.06.2026
Temporary employment agency activities and other human resource provisions

O. H. SIMLENES AS

Org. no. 921158718 Limited company (AS) Askøy Incorporated 2018 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK 0
Equity NOK 30,000
Incorporated 2018
Share capital NOK 30,000

O. H. SIMLENES AS is registered as a limited company in Askøy, Vestland with organisation number 921158718. The business is classified under temporary employment agency activities and other human resource provisions (NACE 78.200). The company was incorporated in 2018. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Drive utleige av ingeniørkompetanse.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK 0 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK 0
Equity
NOK 30,000
Est. value
NOK 43,000

Financial health · 2025

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

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

Who owns O. H. SIMLENES AS?

OVE HENNING SIMLENES
O. H. SIMLENES AS
NOK 0 rev. · NOK 0 profit

O. H. SIMLENES AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about O. H. SIMLENES AS

Who owns O. H. SIMLENES AS?

OVE HENNING SIMLENES is the largest registered owner, with 100.0%.

What is the revenue of O. H. SIMLENES AS?

O. H. SIMLENES AS had revenue of NOK 0 in 2025.

Who is the general manager of O. H. SIMLENES AS?

Ove Henning Simlenes is registered as general manager of O. H. SIMLENES AS.

Where is O. H. SIMLENES AS based?

O. H. SIMLENES 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.