BIZTRAC BETA
Provision of domestic personal service activities

ASKIM HUS OG HAGEARBEID AS

Org. no. 934055969 Limited company (AS) Indre Østfold Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 21,000
Operating profit NOK 20,000
Equity NOK 41,000
Incorporated 2024
Share capital NOK 30,000

ASKIM HUS OG HAGEARBEID AS is registered as a limited company in Indre Østfold, Østfold with organisation number 934055969. The business is classified under provision of domestic personal service activities (NACE 96.910). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Alt innen hagearbeid som plenklipping, beskjæring av hekker og trær, snøbrøyting. Rydding av dødsbo og annet. Samt mindre transportoppdrag.”. The most recent filed accounts, for the 2025 financial year, show NOK 21,000 in revenue and NOK 20,000 in operating profit.

Key figures · 2025

Revenue
NOK 21,000
Operating profit
NOK 20,000
Equity
NOK 41,000
Est. value
NOK 88,000

Financial health · 2024

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

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

Who owns ASKIM HUS OG HAGEARBEID AS?

BJØRN INGAR ARNESEN
ASKIM HUS OG HAGEARBEID AS
NOK 21,000 rev. · NOK 20,000 profit

ASKIM HUS OG HAGEARBEID AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about ASKIM HUS OG HAGEARBEID AS

Who owns ASKIM HUS OG HAGEARBEID AS?

BJØRN INGAR ARNESEN is the largest registered owner, with 50.0%.

What is the revenue of ASKIM HUS OG HAGEARBEID AS?

ASKIM HUS OG HAGEARBEID AS had revenue of NOK 21,000 in 2025.

Where is ASKIM HUS OG HAGEARBEID AS based?

ASKIM HUS OG HAGEARBEID AS has its business address in Askim.

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.