BIZTRAC BETA
COMPANY REGISTER PROFILE
997080211 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 02.09.2026
Site preparation

HANS BIRKELAND AS

Org. no. 997080211 Limited company (AS) Lyngdal Incorporated 2011 Active
Ownership graph ↗
Revenue 2025 NOK 85,000
Operating profit NOK −498,000
Equity NOK 11.2m
Incorporated 2011
Share capital NOK 100,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−498k kr).

HANS BIRKELAND AS is registered as a limited company in Lyngdal, Agder with organisation number 997080211. The business is classified under site preparation (NACE 43.120). The company was incorporated in 2011. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Maskinentreprenør, skogbruk, samt alt som står i naturlig forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 85,000 in revenue and NOK −498,000 in operating profit.

Key figures · 2025

Revenue
NOK 85,000
▲ +50 %
Operating profit
NOK −498,000
▲ +4 %
Equity
NOK 11.2m
▲ +3 %
Est. value
NOK 6.5m

Financial health · 2025

Liquidity
35.08
Very good
Current assets ÷ current liabilities
Profitability
4.7%
Weak
Return on total assets
Solidity
96.9%
Very good
Equity as a share of total capital

Who owns HANS BIRKELAND AS?

HANS BIRKELAND AS
NOK 85,000 rev. · NOK −498,000 profit

HANS BIRKELAND AS has 1 registered shareholder:

All shareholders and roles →

Which companies does HANS BIRKELAND AS own?

HANS BIRKELAND AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about HANS BIRKELAND AS

Who owns HANS BIRKELAND AS?

HANS BIRKELAND is the largest registered owner, with 100.0%.

What is the revenue of HANS BIRKELAND AS?

HANS BIRKELAND AS had revenue of NOK 85,000 in 2025.

Where is HANS BIRKELAND AS based?

HANS BIRKELAND AS has its business address in Lyngdal.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 02.09.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.