BIZTRAC BETA
Sawmilling and planing of wood

GS SAG OG MASKIN AS

Org. no. 926808559 Limited company (AS) Flekkefjord Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 NOK 229,000
Operating profit NOK −18,000
Equity NOK −206,000
Incorporated 2021
Share capital NOK 30,000

Signals

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

GS SAG OG MASKIN AS is registered as a limited company in Flekkefjord, Agder with organisation number 926808559. The business is classified under sawmilling and planing of wood (NACE 16.110). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 10 shares. The company's stated purpose is: “Sage materialer fra tømmer. Inkludert å kappe tømmer selv fra skogen. Lage prefabrikerte kit. Salg av materialer.”. The most recent filed accounts, for the 2025 financial year, show NOK 229,000 in revenue and NOK −18,000 in operating profit.

Key figures · 2025

Revenue
NOK 229,000
Operating profit
NOK −18,000
Equity
NOK −206,000

Financial health · 2025

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

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

Who owns GS SAG OG MASKIN AS?

GLG HOLDING AS
GS SAG OG MASKIN AS
NOK 229,000 rev. · NOK −18,000 profit

GS SAG OG MASKIN AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about GS SAG OG MASKIN AS

Who owns GS SAG OG MASKIN AS?

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

What is the revenue of GS SAG OG MASKIN AS?

GS SAG OG MASKIN AS had revenue of NOK 229,000 in 2025.

Where is GS SAG OG MASKIN AS based?

GS SAG OG MASKIN AS has its business address in Flekkefjord.

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.