biztrac. BETA
COMPANY REGISTER PROFILE
932005468 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Development of building projects

SPTU TOMT 15.1 AS

Org. no. 932005468 Limited company (AS) Kristiansand Incorporated 2023 Active
Revenue 2025 NOK 0
Operating profit NOK −20,000
Equity NOK 127,000
Incorporated 2023
Share capital NOK 30,000

Signals

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

SPTU TOMT 15.1 AS is registered as a limited company in Kristiansand, Agder with organisation number 932005468. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 30000 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.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −20,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −20,000
▼ −26 %
Equity
NOK 127,000
▼ −13 %
Est. value
NOK 116,000

Financial health · 2025

Liquidity
–
Not available
Current assets ÷ current liabilities
Profitability
-0.4%
Not satisfactory
Return on total assets
Solidity
2.6%
Not satisfactory
Equity as a share of total capital

Who owns SPTU TOMT 15.1 AS?

SPTU TOMT 15.1 AS
NOK 0 rev. · NOK −20,000 profit

SPTU TOMT 15.1 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SPTU TOMT 15.1 AS

Who owns SPTU TOMT 15.1 AS?

FRØYSAA HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of SPTU TOMT 15.1 AS?

SPTU TOMT 15.1 AS had revenue of NOK 0 in 2025.

Where is SPTU TOMT 15.1 AS based?

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

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.