BIZTRAC BETA
Buying and selling of own real estate

TØMRER SIMEN SKINMO AS

Org. no. 913343948 Limited company (AS) Larvik Incorporated 2014 Active
Ownership graph ↗
Revenue 2025 NOK 12.2m
Operating profit NOK 1.7m
Equity NOK 3.0m
Incorporated 2014
Share capital NOK 30,000

TØMRER SIMEN SKINMO AS is registered as a limited company in Larvik, Vestfold with organisation number 913343948. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2014. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Kjøp, salg og produksjon i eiendom og landbruk, samt eierinteresser og utvikling av eiendom, tømrer- og snekkertjenester, og det som naturlig hører sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 12.2m in revenue and NOK 1.7m in operating profit.

Key figures · 2025

Revenue
NOK 12.2m
Operating profit
NOK 1.7m
Equity
NOK 3.0m
Est. value
NOK 6.4m

Financial health · 2025

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

Who owns TØMRER SIMEN SKINMO AS?

SIMEN ANTONISEN SKINMO
TØMRER SIMEN SKINMO AS
NOK 12.2m rev. · NOK 1.7m profit

TØMRER SIMEN SKINMO AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TØMRER SIMEN SKINMO AS

Who owns TØMRER SIMEN SKINMO AS?

SIMEN ANTONISEN SKINMO is the largest registered owner, with 100.0%.

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

TØMRER SIMEN SKINMO AS had revenue of NOK 12.2m in 2025.

Who is the general manager of TØMRER SIMEN SKINMO AS?

Simen Antonisen Skinmo is registered as general manager of TØMRER SIMEN SKINMO AS.

Where is TØMRER SIMEN SKINMO AS based?

TØMRER SIMEN SKINMO AS has its business address in Larvik.

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.