BIZTRAC BETA
Operation of gravel and sand pits and mining of clay and kaolin

BUGTEN SANDTAK AS

Org. no. 979927835 Limited company (AS) Skien Incorporated 1997 Active
Ownership graph ↗
Revenue 2025 NOK 6.3m
Operating profit NOK −51,000
Equity NOK 1.3m
Incorporated 1997
Employees 6
Share capital NOK 400,000

Signals

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

BUGTEN SANDTAK AS is registered as a limited company in Skien, Telemark with organisation number 979927835. The business is classified under operation of gravel and sand pits and mining of clay and kaolin (NACE 08.120). The company was incorporated in 1997 and has 6 registered employees. Registered share capital is NOK 400,000, divided into 4000 shares. The company's stated purpose is: “Foredling av sand, transport, o.l.”. The most recent filed accounts, for the 2025 financial year, show NOK 6.3m in revenue and NOK −51,000 in operating profit.

Key figures · 2025

Revenue
NOK 6.3m
Operating profit
NOK −51,000
Equity
NOK 1.3m
Est. value
NOK 5.3m

Financial health · 2025

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

Who owns BUGTEN SANDTAK AS?

JAN TORE RØNNINGEN
BUGTEN SANDTAK AS
NOK 6.3m rev. · NOK −51,000 profit

BUGTEN SANDTAK AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about BUGTEN SANDTAK AS

Who owns BUGTEN SANDTAK AS?

JAN TORE RØNNINGEN is the largest registered owner, with 51.0%.

What is the revenue of BUGTEN SANDTAK AS?

BUGTEN SANDTAK AS had revenue of NOK 6.3m in 2025.

Who is the general manager of BUGTEN SANDTAK AS?

Jan Tore Rønningen is registered as general manager of BUGTEN SANDTAK AS.

Where is BUGTEN SANDTAK AS based?

BUGTEN SANDTAK AS has its business address in Skien.

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.