BIZTRAC BETA
Site preparation

J. AJER MASKIN AS

Org. no. 924492546 Limited company (AS) Nome Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 643,000
Operating profit NOK 80,000
Equity NOK 7,000
Incorporated 2020
Share capital NOK 30,000

J. AJER MASKIN AS is registered as a limited company in Nome, Telemark with organisation number 924492546. The business is classified under site preparation (NACE 43.120). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Alt mulig innen gravearbeid og masseforflytning, sveising og reparasjonsarbeid, samt andre produkter/tjenester som naturlig hører til dette, herunder å delta i andre selskap med lignende virksomhet, og kjøp og salg av aksjer eller på annen måte gjøre seg interessert i andre foretak. Selskapet kan også drive med kjøp/drift av fast eiendom.”. The most recent filed accounts, for the 2025 financial year, show NOK 643,000 in revenue and NOK 80,000 in operating profit.

Key figures · 2025

Revenue
NOK 643,000
Operating profit
NOK 80,000
Equity
NOK 7,000
Est. value
NOK 167,000

Financial health · 2024

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

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

Who owns J. AJER MASKIN AS?

JOAKIM AJER
J. AJER MASKIN AS
NOK 643,000 rev. · NOK 80,000 profit

J. AJER MASKIN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about J. AJER MASKIN AS

Who owns J. AJER MASKIN AS?

JOAKIM AJER is the largest registered owner, with 100.0%.

What is the revenue of J. AJER MASKIN AS?

J. AJER MASKIN AS had revenue of NOK 643,000 in 2025.

Where is J. AJER MASKIN AS based?

J. AJER MASKIN AS has its business address in Lunde.

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.