BIZTRAC BETA
Other cleaning activities

DALHEIKNEIKA BRØYTESERVICE AS

Org. no. 936280595 Limited company (AS) Tvedestrand Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 105,000
Operating profit NOK 71,000
Equity NOK 86,000
Incorporated 2025
Share capital NOK 30,000

Signals

1 flags
  • Nystiftet selskap Selskapet ble stiftet 2025-09-01.

DALHEIKNEIKA BRØYTESERVICE AS is registered as a limited company in Tvedestrand, Agder with organisation number 936280595. The business is classified under other cleaning activities (NACE 81.230). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Drive vintervedlikehold av vei og utleie av traktortjenester samt oppgaver som faller naturlig med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 105,000 in revenue and NOK 71,000 in operating profit.

Key figures · 2025

Revenue
NOK 105,000
Operating profit
NOK 71,000
Equity
NOK 86,000
Est. value
NOK 263,000

Financial health · 2025

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

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

Who owns DALHEIKNEIKA BRØYTESERVICE AS?

BJØRN INGE HANSEN
DALHEIKNEIKA BRØYTESERVICE AS
NOK 105,000 rev. · NOK 71,000 profit

DALHEIKNEIKA BRØYTESERVICE AS has 4 registered shareholders:

All shareholders and roles →

Frequently asked questions about DALHEIKNEIKA BRØYTESERVICE AS

Who owns DALHEIKNEIKA BRØYTESERVICE AS?

BJØRN INGE HANSEN is the largest registered owner, with 25.0%.

What is the revenue of DALHEIKNEIKA BRØYTESERVICE AS?

DALHEIKNEIKA BRØYTESERVICE AS had revenue of NOK 105,000 in 2025.

Where is DALHEIKNEIKA BRØYTESERVICE AS based?

DALHEIKNEIKA BRØYTESERVICE AS has its business address in Gjeving.

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.