BIZTRAC BETA
Quarrying of ornamental stone, limestone, gypsum, slate and other stone

BAMBLE PUKKSERVICE AS

Org. no. 925833657 Limited company (AS) Bamble Incorporated 2020 Active
Ownership graph ↗
Revenue 2024 NOK 7.9m
Operating profit NOK 520,000
Equity NOK 6.1m
Incorporated 2020
Share capital NOK 250,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

BAMBLE PUKKSERVICE AS is registered as a limited company in Bamble, Telemark with organisation number 925833657. The business is classified under quarrying of ornamental stone, limestone, gypsum, slate and other stone (NACE 08.110). The company was incorporated in 2020. Registered share capital is NOK 250,000, divided into 100 shares. The company's stated purpose is: “Knusing av pukk og stein. Salg av knuste masser, jord og leirmasser. Uttak av naturstein.”. The most recent filed accounts, for the 2024 financial year, show NOK 7.9m in revenue and NOK 520,000 in operating profit.

Key figures · 2024

Revenue
NOK 7.9m
Operating profit
NOK 520,000
Equity
NOK 6.1m
Est. value
NOK 4.4m

Financial health · 2024

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

Who owns BAMBLE PUKKSERVICE AS?

TELLEFSEN INVEST AS
BAMBLE PUKKSERVICE AS
NOK 7.9m rev. · NOK 520,000 profit

BAMBLE PUKKSERVICE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BAMBLE PUKKSERVICE AS

Who owns BAMBLE PUKKSERVICE AS?

TELLEFSEN INVEST AS is the largest registered owner, with 100.0%.

What is the revenue of BAMBLE PUKKSERVICE AS?

BAMBLE PUKKSERVICE AS had revenue of NOK 7.9m in 2024.

Where is BAMBLE PUKKSERVICE AS based?

BAMBLE PUKKSERVICE AS has its business address in Stathelle.

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.