BIZTRAC BETA
Rental and operating of own or leased real estate

TOLVKANTEN AS

Org. no. 987649038 Limited company (AS) Tønsberg Incorporated 2004 Active
Ownership graph ↗
Revenue 2024 NOK 746,000
Operating profit NOK −32,000
Equity NOK 655,000
Incorporated 2004
Share capital NOK 100,000

Signals

3 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−32k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.
  • Nylig endring 2026-04-27 Adresseendring registrert 2026-04-27.

TOLVKANTEN AS is registered as a limited company in Tønsberg, Vestfold with organisation number 987649038. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2004. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Å eie og drive fast eiendom og dertil tilhørende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 746,000 in revenue and NOK −32,000 in operating profit.

Key figures · 2024

Revenue
NOK 746,000
Operating profit
NOK −32,000
Equity
NOK 655,000
Est. value
NOK 598,000

Financial health · 2024

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

Who owns TOLVKANTEN AS?

KILEN HANDELSPARK AS
TOLVKANTEN AS
NOK 746,000 rev. · NOK −32,000 profit

TOLVKANTEN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TOLVKANTEN AS

Who owns TOLVKANTEN AS?

KILEN HANDELSPARK AS is the largest registered owner, with 100.0%.

What is the revenue of TOLVKANTEN AS?

TOLVKANTEN AS had revenue of NOK 746,000 in 2024.

Where is TOLVKANTEN AS based?

TOLVKANTEN AS has its business address in Tønsberg.

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.