BIZTRAC BETA
Site preparation

TD MASKIN PUKK AS

Org. no. 919926406 Limited company (AS) Bygland Incorporated 2017 Active
Ownership graph ↗
Revenue 2024 NOK 2.1m
Operating profit NOK −631,000
Equity NOK −3.1m
Incorporated 2017
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−3,1 mill kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−631k kr).

TD MASKIN PUKK AS is registered as a limited company in Bygland, Agder with organisation number 919926406. The business is classified under site preparation (NACE 43.120). The company was incorporated in 2017. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Entreprenør- og transportverksemd og alt som står i forbindelse med dette. Vidare kjøp og salg av maskinar og utstyr, utleige av utstyr og personell og drift av massetak.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.1m in revenue and NOK −631,000 in operating profit.

Key figures · 2024

Revenue
NOK 2.1m
Operating profit
NOK −631,000
Equity
NOK −3.1m

Financial health · 2024

Liquidity
3.04
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-81.1%
Weak
Equity as a share of total capital

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

Who owns TD MASKIN PUKK AS?

DRENG OSE HOLDING AS
TD MASKIN PUKK AS
NOK 2.1m rev. · NOK −631,000 profit

TD MASKIN PUKK AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about TD MASKIN PUKK AS

Who owns TD MASKIN PUKK AS?

DRENG OSE HOLDING AS is the largest registered owner, with 50.0%.

What is the revenue of TD MASKIN PUKK AS?

TD MASKIN PUKK AS had revenue of NOK 2.1m in 2024.

Where is TD MASKIN PUKK AS based?

TD MASKIN PUKK AS has its business address in Bygland.

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.