BIZTRAC BETA
Support services to forestry

BB SKOGPLEIE AS

Org. no. 936514472 Limited company (AS) Krødsherad Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 60,000
Operating profit NOK −7,000
Equity NOK 88,000
Incorporated 2025
Share capital NOK 100,000

Signals

2 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−7k kr).
  • Nystiftet selskap Selskapet ble stiftet 2025-10-28.

BB SKOGPLEIE AS is registered as a limited company in Krødsherad, Buskerud with organisation number 936514472. The business is classified under support services to forestry (NACE 02.400). The company was incorporated in 2025. Registered share capital is NOK 100,000, divided into 100000 shares. The company's stated purpose is: “Tilby skogsentreprenørtjenester, inkludert, men ikke begrenset til, tynning av skog, skogskjøtsel, planting, rydding, og andre relaterte tjenester.”. The most recent filed accounts, for the 2025 financial year, show NOK 60,000 in revenue and NOK −7,000 in operating profit.

Key figures · 2025

Revenue
NOK 60,000
Operating profit
NOK −7,000
Equity
NOK 88,000
Est. value
NOK 84,000

Financial health · 2025

Liquidity
-0.39
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
4.7%
Weak
Equity as a share of total capital

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

Who owns BB SKOGPLEIE AS?

SIGMUND BERGAN AS
BB SKOGPLEIE AS
NOK 60,000 rev. · NOK −7,000 profit

BB SKOGPLEIE AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about BB SKOGPLEIE AS

Who owns BB SKOGPLEIE AS?

SIGMUND BERGAN AS is the largest registered owner, with 50.0%.

What is the revenue of BB SKOGPLEIE AS?

BB SKOGPLEIE AS had revenue of NOK 60,000 in 2025.

Where is BB SKOGPLEIE AS based?

BB SKOGPLEIE AS has its business address in Noresund.

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.