BIZTRAC BETA
Construction of residential and non-residential buildings

SIVERTSEN SNIKKERI AS

Org. no. 928654362 Limited company (AS) Froland Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 586,000
Operating profit NOK 60,000
Equity NOK 119,000
Incorporated 2022
Share capital NOK 30,000

SIVERTSEN SNIKKERI AS is registered as a limited company in Froland, Agder with organisation number 928654362. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Tømring og snekkervirksomhet i nybygg eller restaurering av eldre bygg eller annet tilsvarende tømrerarbeid.”. The most recent filed accounts, for the 2025 financial year, show NOK 586,000 in revenue and NOK 60,000 in operating profit.

Key figures · 2025

Revenue
NOK 586,000
Operating profit
NOK 60,000
Equity
NOK 119,000
Est. value
NOK 256,000

Financial health · 2024

Liquidity
2.14
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
67.4%
Very good
Equity as a share of total capital

Who owns SIVERTSEN SNIKKERI AS?

ØYVIND SIVERTSEN
SIVERTSEN SNIKKERI AS
NOK 586,000 rev. · NOK 60,000 profit

SIVERTSEN SNIKKERI AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SIVERTSEN SNIKKERI AS

Who owns SIVERTSEN SNIKKERI AS?

ØYVIND SIVERTSEN is the largest registered owner, with 100.0%.

What is the revenue of SIVERTSEN SNIKKERI AS?

SIVERTSEN SNIKKERI AS had revenue of NOK 586,000 in 2025.

Who is the general manager of SIVERTSEN SNIKKERI AS?

Øyvind Sivertsen is registered as general manager of SIVERTSEN SNIKKERI AS.

Where is SIVERTSEN SNIKKERI AS based?

SIVERTSEN SNIKKERI AS has its business address in Froland.

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.