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

SPINNVILL EIENDOM AS

Org. no. 922808813 Limited company (AS) Lindesnes Incorporated 2019 Active
Revenue 2025 NOK 353,000
Operating profit NOK −155,000
Equity NOK −249,000
Incorporated 2019
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−249k kr).

SPINNVILL EIENDOM AS is registered as a limited company in Lindesnes, Agder with organisation number 922808813. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Drift og utleie av næringseiendom.”. The most recent filed accounts, for the 2025 financial year, show NOK 353,000 in revenue and NOK −155,000 in operating profit.

Key figures · 2025

Revenue
NOK 353,000
▼ −36 %
Operating profit
NOK −155,000
▼ −154 %
Equity
NOK −249,000
▼ −274 %
Est. value
NOK 475,000

Financial health · 2025

Liquidity
0.57
Weak
Current assets ÷ current liabilities
Profitability
-2.3%
Not satisfactory
Return on total assets
Solidity
-3.0%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns SPINNVILL EIENDOM AS?

SPINNVILL EIENDOM AS
NOK 353,000 rev. · NOK −155,000 profit

SPINNVILL EIENDOM AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about SPINNVILL EIENDOM AS

Who owns SPINNVILL EIENDOM AS?

MOLBROOK CAPITAL AS is the largest registered owner, with 50.0%.

What is the revenue of SPINNVILL EIENDOM AS?

SPINNVILL EIENDOM AS had revenue of NOK 353,000 in 2025.

Where is SPINNVILL EIENDOM AS based?

SPINNVILL EIENDOM AS has its business address in Mandal.

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.