BIZTRAC BETA
Logging

JAN ÅGE SANDBÆK AS

Org. no. 976253701 Limited company (AS) Flesberg Incorporated 1996 Active
Ownership graph ↗
Revenue 2025 NOK 6.0m
Operating profit NOK −384,000
Equity NOK −700,000
Incorporated 1996
Share capital NOK 900,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−700k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−384k kr).

JAN ÅGE SANDBÆK AS is registered as a limited company in Flesberg, Buskerud with organisation number 976253701. The business is classified under logging (NACE 02.200). The company was incorporated in 1996. Registered share capital is NOK 900,000, divided into 9000 shares. The company's stated purpose is: “Transport, handel og produksjon og alt hva hermed står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 6.0m in revenue and NOK −384,000 in operating profit.

Key figures · 2025

Revenue
NOK 6.0m
Operating profit
NOK −384,000
Equity
NOK −700,000

Financial health · 2025

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

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

Who owns JAN ÅGE SANDBÆK AS?

Jan Åge Sandbæk
JAN ÅGE SANDBÆK AS
NOK 6.0m rev. · NOK −384,000 profit

JAN ÅGE SANDBÆK AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about JAN ÅGE SANDBÆK AS

Who owns JAN ÅGE SANDBÆK AS?

Jan Åge Sandbæk is the largest registered owner, with 100.0%.

What is the revenue of JAN ÅGE SANDBÆK AS?

JAN ÅGE SANDBÆK AS had revenue of NOK 6.0m in 2025.

Who is the general manager of JAN ÅGE SANDBÆK AS?

Kjetil Sandbæk is registered as general manager of JAN ÅGE SANDBÆK AS.

Where is JAN ÅGE SANDBÆK AS based?

JAN ÅGE SANDBÆK AS has its business address in Lampeland.

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.