BIZTRAC BETA
Wholesale of mining, construction and civil engineering machinery

ISOMESTER AS

Org. no. 835339122 Limited company (AS) Halden Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 3.5m
Operating profit NOK 236,000
Equity NOK 35,000
Incorporated 2025
Share capital NOK 30,000

ISOMESTER AS is registered as a limited company in Halden, Østfold with organisation number 835339122. The business is classified under wholesale of mining, construction and civil engineering machinery (NACE 46.630). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Import/eksport, salg av maskiner og utstyr til bygge-bransjen, samt alt som står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.5m in revenue and NOK 236,000 in operating profit.

Key figures · 2025

Revenue
NOK 3.5m
Operating profit
NOK 236,000
Equity
NOK 35,000
Est. value
NOK 950,000

Financial health · 2025

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

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

Who owns ISOMESTER AS?

K. KOPPERUD AS
ISOMESTER AS
NOK 3.5m rev. · NOK 236,000 profit

ISOMESTER AS has 1 registered shareholder:

All shareholders and roles →

Group structure

ISOMESTER AS er morselskap for 5 datterselskaper:

Frequently asked questions about ISOMESTER AS

Who owns ISOMESTER AS?

K. KOPPERUD AS is the largest registered owner, with 100.0%.

What is the revenue of ISOMESTER AS?

ISOMESTER AS had revenue of NOK 3.5m in 2025.

Who is the general manager of ISOMESTER AS?

Kristher Kopperud is registered as general manager of ISOMESTER AS.

Where is ISOMESTER AS based?

ISOMESTER AS has its business address in Berg I Østfold.

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.