BIZTRAC BETA
COMPANY REGISTER PROFILE
929317866 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Development of building projects

SPTU TOMT 15.2 AS

Org. no. 929317866 Limited company (AS) Kristiansand Incorporated 2022 Active
Ownership graph ↗
Equity NOK 170,000
Incorporated 2022
Share capital NOK 134,000

SPTU TOMT 15.2 AS is registered as a limited company in Kristiansand, Agder with organisation number 929317866. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2022. Registered share capital is NOK 134,000, divided into 134000 shares. The company's stated purpose is: “Eiendomsutvikling og tomtesalg og deltakelse i andre virksomheter ved aksjeeie eller på annen måte og det som står i forbindelse med dette.”.

Key figures · 2025

Equity
NOK 170,000
Est. value
NOK 155,000

Financial health · 2025

Liquidity
1.03
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
2.8%
Not satisfactory
Equity as a share of total capital

Who owns SPTU TOMT 15.2 AS?

SPTU TOMT 15.2 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SPTU TOMT 15.2 AS

Who owns SPTU TOMT 15.2 AS?

SØRLANDSPARKEN HOLDING AS is the largest registered owner, with 100.0%.

Where is SPTU TOMT 15.2 AS based?

SPTU TOMT 15.2 AS has its business address in Kristiansand S.

Property

Business address Fidjeåsen 18, 4639 Kristiansand S
Cadastral unit 4204-95/332/0/0
Building Stort frittliggende boligbygg på 5 etg el mer · 34 units

9 companies are registered at this address.

The address this company is registered at, from the company register and matched against the cadastre. It does not say who owns the property — a company may be a tenant, and the address is often its accountant's. Source: Brønnøysundregistrene and © Kartverket.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 02.09.2026.

Report a problem

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