BIZTRAC BETA
Operation of gravel and sand pits and mining of clay and kaolin

AREMARK PUKKVERK AS

Org. no. 994561529 Limited company (AS) Indre Østfold Incorporated 2009 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK 0
Equity NOK 321,000
Incorporated 2009
Share capital NOK 100,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

AREMARK PUKKVERK AS is registered as a limited company in Indre Østfold, Østfold with organisation number 994561529. The business is classified under operation of gravel and sand pits and mining of clay and kaolin (NACE 08.120). The company was incorporated in 2009. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Drift av pukkverk og det som naturlig hører inn under dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK 0 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK 0
Equity
NOK 321,000
Est. value
NOK 317,000

Financial health · 2024

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

Who owns AREMARK PUKKVERK AS?

HØITOMT FJELLBORING AS
AREMARK PUKKVERK AS
NOK 0 rev. · NOK 0 profit

AREMARK PUKKVERK AS has 1 registered shareholder:

All shareholders and roles →

Group structure

AREMARK PUKKVERK AS er morselskap for 2 datterselskaper:

Frequently asked questions about AREMARK PUKKVERK AS

Who owns AREMARK PUKKVERK AS?

HØITOMT FJELLBORING AS is the largest registered owner, with 100.0%.

What is the revenue of AREMARK PUKKVERK AS?

AREMARK PUKKVERK AS had revenue of NOK 0 in 2024.

Where is AREMARK PUKKVERK AS based?

AREMARK PUKKVERK AS has its business address in Trøgstad.

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.