BIZTRAC BETA
Joinery installation

ISSKET SNEKKERSERVICE AS

Org. no. 923334599 Limited company (AS) Meråker Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 474,000
Operating profit NOK 6,000
Equity NOK 29,000
Incorporated 2019
Share capital NOK 30,000

ISSKET SNEKKERSERVICE AS is registered as a limited company in Meråker, Trøndelag with organisation number 923334599. The business is classified under joinery installation (NACE 43.320). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 3000 shares. The company's stated purpose is: “Å utføre små og mellomstore snekkeroppdrag og annet som naturlig faller sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 474,000 in revenue and NOK 6,000 in operating profit.

Key figures · 2025

Revenue
NOK 474,000
Operating profit
NOK 6,000
Equity
NOK 29,000
Est. value
NOK 38,000

Financial health · 2025

Liquidity
1.11
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
10.1%
Weak
Equity as a share of total capital

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

Who owns ISSKET SNEKKERSERVICE AS?

ISSAM NAAMEH
ISSKET SNEKKERSERVICE AS
NOK 474,000 rev. · NOK 6,000 profit

ISSKET SNEKKERSERVICE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ISSKET SNEKKERSERVICE AS

Who owns ISSKET SNEKKERSERVICE AS?

ISSAM NAAMEH is the largest registered owner, with 100.0%.

What is the revenue of ISSKET SNEKKERSERVICE AS?

ISSKET SNEKKERSERVICE AS had revenue of NOK 474,000 in 2025.

Who is the general manager of ISSKET SNEKKERSERVICE AS?

Issam Naameh is registered as general manager of ISSKET SNEKKERSERVICE AS.

Where is ISSKET SNEKKERSERVICE AS based?

ISSKET SNEKKERSERVICE AS has its business address in Meråker.

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.