BIZTRAC BETA
Site preparation

SKIEN TOMTESELSKAP AS

Org. no. 930463701 Limited company (AS) Skien Incorporated 1964 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −40,000
Equity NOK 3.1m
Incorporated 1964
Share capital NOK 100,000

Signals

2 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−40k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

SKIEN TOMTESELSKAP AS is registered as a limited company in Skien, Telemark with organisation number 930463701. The business is classified under site preparation (NACE 43.120). The company was incorporated in 1964. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Erverve område i Skien passende til tomter, gjøre disse byggeklare og overdra dem til tomtesøkere, samt å påta seg saneringsoppgaver innen kommunen.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −40,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −40,000
Equity
NOK 3.1m
Est. value
NOK 3.2m

Financial health · 2025

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

Who owns SKIEN TOMTESELSKAP AS?

SKIEN KOMMUNE
SKIEN TOMTESELSKAP AS
NOK 0 rev. · NOK −40,000 profit

SKIEN TOMTESELSKAP AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SKIEN TOMTESELSKAP AS

Who owns SKIEN TOMTESELSKAP AS?

SKIEN KOMMUNE is the largest registered owner, with 100.0%.

What is the revenue of SKIEN TOMTESELSKAP AS?

SKIEN TOMTESELSKAP AS had revenue of NOK 0 in 2025.

Where is SKIEN TOMTESELSKAP AS based?

SKIEN TOMTESELSKAP AS has its business address in Skien.

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.