BIZTRAC BETA
Construction of residential and non-residential buildings

TØMRER SIMEN ANDERSEN AS

Org. no. 933303462 Limited company (AS) Larvik Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 1.4m
Operating profit NOK −52,000
Equity NOK −31,000
Incorporated 2024
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−31k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−52k kr).

TØMRER SIMEN ANDERSEN AS is registered as a limited company in Larvik, Vestfold with organisation number 933303462. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Utføre tømrerarbeid.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.4m in revenue and NOK −52,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.4m
Operating profit
NOK −52,000
Equity
NOK −31,000

Financial health · 2025

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

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

Who owns TØMRER SIMEN ANDERSEN AS?

SIMEN-ANDRÈ STENSRØD ANDERSEN
TØMRER SIMEN ANDERSEN AS
NOK 1.4m rev. · NOK −52,000 profit

TØMRER SIMEN ANDERSEN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TØMRER SIMEN ANDERSEN AS

Who owns TØMRER SIMEN ANDERSEN AS?

SIMEN-ANDRÈ STENSRØD ANDERSEN is the largest registered owner, with 100.0%.

What is the revenue of TØMRER SIMEN ANDERSEN AS?

TØMRER SIMEN ANDERSEN AS had revenue of NOK 1.4m in 2025.

Where is TØMRER SIMEN ANDERSEN AS based?

TØMRER SIMEN ANDERSEN AS has its business address in Helgeroa.

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.