BIZTRAC BETA
Site preparation

IHLANG ARBEIDSLAG AS

Org. no. 922404836 Limited company (AS) Nes Incorporated 2019 Active
Ownership graph ↗
Operating profit NOK −23,000
Equity NOK 2.1m
Incorporated 2019
Share capital NOK 30,000

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−23k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

IHLANG ARBEIDSLAG AS is registered as a limited company in Nes, Akershus with organisation number 922404836. The business is classified under site preparation (NACE 43.120). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Investering i andre selskaper, 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.”.

Key figures · 2024

Operating profit
NOK −23,000
Equity
NOK 2.1m
Est. value
NOK 2.1m

Financial health · 2024

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

Who owns IHLANG ARBEIDSLAG AS?

THOMAS IHLANG
IHLANG ARBEIDSLAG AS
· NOK −23,000 profit

IHLANG ARBEIDSLAG AS has 1 registered shareholder:

All shareholders and roles →

Which companies does IHLANG ARBEIDSLAG AS own?

IHLANG ARBEIDSLAG AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about IHLANG ARBEIDSLAG AS

Who owns IHLANG ARBEIDSLAG AS?

THOMAS IHLANG is the largest registered owner, with 100.0%.

Who is the general manager of IHLANG ARBEIDSLAG AS?

Thomas Ihlang is registered as general manager of IHLANG ARBEIDSLAG AS.

Where is IHLANG ARBEIDSLAG AS based?

IHLANG ARBEIDSLAG AS has its business address in Skogbygda.

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.