BIZTRAC BETA
Joinery installation

SHAMON SNEKKERI AS

Org. no. 932750120 Limited company (AS) Fredrikstad Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 1.4m
Operating profit NOK −399,000
Equity NOK −380,000
Incorporated 2023
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−380k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−399k kr).

SHAMON SNEKKERI AS is registered as a limited company in Fredrikstad, Østfold with organisation number 932750120. The business is classified under joinery installation (NACE 43.320). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Produksjon av møbler.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.4m in revenue and NOK −399,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.4m
Operating profit
NOK −399,000
Equity
NOK −380,000

Financial health · 2024

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

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

Who owns SHAMON SNEKKERI AS?

SHAWK THAIR SHAMON
SHAMON SNEKKERI AS
NOK 1.4m rev. · NOK −399,000 profit

SHAMON SNEKKERI AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SHAMON SNEKKERI AS

Who owns SHAMON SNEKKERI AS?

SHAWK THAIR SHAMON is the largest registered owner, with 100.0%.

What is the revenue of SHAMON SNEKKERI AS?

SHAMON SNEKKERI AS had revenue of NOK 1.4m in 2024.

Who is the general manager of SHAMON SNEKKERI AS?

Shawk Thair Shamon is registered as general manager of SHAMON SNEKKERI AS.

Where is SHAMON SNEKKERI AS based?

SHAMON SNEKKERI AS has its business address in Fredrikstad.

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.