BIZTRAC BETA
Combined facilities support activities

ARGO ARBEID AS

Org. no. 929334183 Limited company (AS) Karmøy Incorporated 2022 Active
Ownership graph ↗
Revenue 2024 NOK 179,000
Operating profit NOK 8,000
Equity NOK 80,000
Incorporated 2022
Share capital NOK 30,000

ARGO ARBEID AS is registered as a limited company in Karmøy, Rogaland with organisation number 929334183. The business is classified under combined facilities support activities (NACE 81.100). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Salg av varer og tjenester, vaktmesterarbeid, utleie av utstyr, utleie og salg av fast eiendom, bilpleie, markedsføring. Fasadearbeid, hage- og utearbeid, transport og logistikk.”. The most recent filed accounts, for the 2024 financial year, show NOK 179,000 in revenue and NOK 8,000 in operating profit.

Key figures · 2024

Revenue
NOK 179,000
Operating profit
NOK 8,000
Equity
NOK 80,000
Est. value
NOK 85,000

Financial health · 2024

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

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

Who owns ARGO ARBEID AS?

MARIUS FISKAAEN
ARGO ARBEID AS
NOK 179,000 rev. · NOK 8,000 profit

ARGO ARBEID AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about ARGO ARBEID AS

Who owns ARGO ARBEID AS?

MARIUS FISKAAEN is the largest registered owner, with 50.0%.

What is the revenue of ARGO ARBEID AS?

ARGO ARBEID AS had revenue of NOK 179,000 in 2024.

Who is the general manager of ARGO ARBEID AS?

Marius Fiskaaen is registered as general manager of ARGO ARBEID AS.

Where is ARGO ARBEID AS based?

ARGO ARBEID AS has its business address in Karmsund.

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.