biztrac. BETA
COMPANY REGISTER PROFILE
942475918 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Rental and operating of own or leased real estate

TOC 3 AS

Org. no. 942475918 Limited company (AS) Larvik Incorporated 1987 Active
Revenue 2025 NOK 1.5m
Operating profit NOK −121,000
Equity NOK 9.2m
Incorporated 1987
Share capital NOK 4.0m

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−121k kr).

TOC 3 AS is registered as a limited company in Larvik, Vestfold with organisation number 942475918. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1987. Registered share capital is NOK 4.0m, divided into 160000 shares. The company's stated purpose is: “Eie og forvalte fast eiendom, kjøpe og selge fast eiendom, samt eie interesser i andre foretak.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.5m in revenue and NOK −121,000 in operating profit.

Former names: APS INVEST AS, KOSMOS AS

Key figures · 2025

Revenue
NOK 1.5m
▼ −32 %
Operating profit
NOK −121,000
▼ −112 %
Equity
NOK 9.2m
▲ +6 %
Est. value
NOK 8.2m

Financial health · 2025

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

Who owns TOC 3 AS?

TOC 3 AS
NOK 1.5m rev. · NOK −121,000 profit

TOC 3 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TOC 3 AS

Who owns TOC 3 AS?

MONTANA AS is the largest registered owner, with 100.0%.

What is the revenue of TOC 3 AS?

TOC 3 AS had revenue of NOK 1.5m in 2025.

Who is the general manager of TOC 3 AS?

Hans Christian Gaarder is registered as general manager of TOC 3 AS.

Where is TOC 3 AS based?

TOC 3 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 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.