BIZTRAC BETA
Development of building projects

R.SAMDAL SNEKKERI AS

Org. no. 918055886 Limited company (AS) Melhus Incorporated 2016 Active
Ownership graph ↗
Revenue 2024 NOK 3.3m
Operating profit NOK 1.7m
Equity NOK 273,000
Incorporated 2016
Share capital NOK 30,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

R.SAMDAL SNEKKERI AS is registered as a limited company in Melhus, Trøndelag with organisation number 918055886. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2016. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Produksjon av trevarer og andre produkter for byggenæringen.”. The most recent filed accounts, for the 2024 financial year, show NOK 3.3m in revenue and NOK 1.7m in operating profit.

Key figures · 2024

Revenue
NOK 3.3m
Operating profit
NOK 1.7m
Equity
NOK 273,000
Est. value
NOK 4.3m

Financial health · 2024

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

Who owns R.SAMDAL SNEKKERI AS?

SAMDAL HOLDING AS
R.SAMDAL SNEKKERI AS
NOK 3.3m rev. · NOK 1.7m profit

R.SAMDAL SNEKKERI AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about R.SAMDAL SNEKKERI AS

Who owns R.SAMDAL SNEKKERI AS?

SAMDAL HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of R.SAMDAL SNEKKERI AS?

R.SAMDAL SNEKKERI AS had revenue of NOK 3.3m in 2024.

Who is the general manager of R.SAMDAL SNEKKERI AS?

Roger Samdal is registered as general manager of R.SAMDAL SNEKKERI AS.

Where is R.SAMDAL SNEKKERI AS based?

R.SAMDAL SNEKKERI AS has its business address in Lundamo.

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.