BIZTRAC BETA
Electrical installation

SIMEN ARNTSEN AS

Org. no. 932487578 Limited company (AS) Høyanger Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 292,000
Operating profit NOK 48,000
Equity NOK 161,000
Incorporated 2023
Share capital NOK 300,000

SIMEN ARNTSEN AS is registered as a limited company in Høyanger, Vestland with organisation number 932487578. The business is classified under electrical installation (NACE 43.210). The company was incorporated in 2023. Registered share capital is NOK 300,000, divided into 300 shares. The company's stated purpose is: “Investere i selskaper og eiendom og alt annet som naturlig faller sammen med dette, herunder å delta i andre selskaper med lignende virksomhet, kjøp og salg av aksjer, eller på annen måte gjøre seg interessert i andre foretagende.”. The most recent filed accounts, for the 2025 financial year, show NOK 292,000 in revenue and NOK 48,000 in operating profit.

Key figures · 2025

Revenue
NOK 292,000
Operating profit
NOK 48,000
Equity
NOK 161,000
Est. value
NOK 169,000

Financial health · 2025

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

Who owns SIMEN ARNTSEN AS?

SIMEN ANDRE ARNTSEN
SIMEN ARNTSEN AS
NOK 292,000 rev. · NOK 48,000 profit

SIMEN ARNTSEN AS has 1 registered shareholder:

All shareholders and roles →

Which companies does SIMEN ARNTSEN AS own?

SIMEN ARNTSEN AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about SIMEN ARNTSEN AS

Who owns SIMEN ARNTSEN AS?

SIMEN ANDRE ARNTSEN is the largest registered owner, with 100.0%.

What is the revenue of SIMEN ARNTSEN AS?

SIMEN ARNTSEN AS had revenue of NOK 292,000 in 2025.

Where is SIMEN ARNTSEN AS based?

SIMEN ARNTSEN AS has its business address in Lavik.

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.