BIZTRAC BETA
Masonry and bricklaying activities

SMÅMURING AS

Org. no. 932600374 Limited company (AS) Birkenes Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 309,000
Operating profit NOK −123
Equity NOK 78,000
Incorporated 2023
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−123 kr).

SMÅMURING AS is registered as a limited company in Birkenes, Agder with organisation number 932600374. The business is classified under masonry and bricklaying activities (NACE 43.910). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Selge varer og tjenester innen murerarbeid - og annet som naturlig sammenfaller med dette - samt deltakelse i andre selskaper, investeringer og nærliggende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 309,000 in revenue and NOK −123 in operating profit.

Key figures · 2024

Revenue
NOK 309,000
Operating profit
NOK −123
Equity
NOK 78,000
Est. value
NOK 140,000

Financial health · 2024

Liquidity
1.74
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
55.6%
Weak
Equity as a share of total capital

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

Who owns SMÅMURING AS?

TOM STANGSTUEN
SMÅMURING AS
NOK 309,000 rev. · NOK −123 profit

SMÅMURING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SMÅMURING AS

Who owns SMÅMURING AS?

TOM STANGSTUEN is the largest registered owner, with 100.0%.

What is the revenue of SMÅMURING AS?

SMÅMURING AS had revenue of NOK 309,000 in 2024.

Who is the general manager of SMÅMURING AS?

Tom Stangstuen is registered as general manager of SMÅMURING AS.

Where is SMÅMURING AS based?

SMÅMURING AS has its business address in Birkeland.

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.