BIZTRAC BETA
Buying and selling of own real estate

SPILLAN EIENDOM AS

Org. no. 916392338 Limited company (AS) Bergen Incorporated 2015 Active
Ownership graph ↗
Revenue 2024 NOK 341,000
Operating profit NOK −972,000
Equity NOK 6.5m
Incorporated 2015
Share capital NOK 780,000

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−972k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

SPILLAN EIENDOM AS is registered as a limited company in Bergen, Vestland with organisation number 916392338. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2015. Registered share capital is NOK 780,000, divided into 1500 shares. The company's stated purpose is: “Salg og kjøp av aksjer, eie aksjer i andre selskaper og kjøp og salg av eiendommer, samt drift av eiendommer.”. The most recent filed accounts, for the 2024 financial year, show NOK 341,000 in revenue and NOK −972,000 in operating profit.

Key figures · 2024

Revenue
NOK 341,000
Operating profit
NOK −972,000
Equity
NOK 6.5m
Est. value
NOK 4.6m

Financial health · 2024

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

Who owns SPILLAN EIENDOM AS?

SPILLAN AS
SPILLAN EIENDOM AS
NOK 341,000 rev. · NOK −972,000 profit

SPILLAN EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SPILLAN EIENDOM AS

Who owns SPILLAN EIENDOM AS?

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

What is the revenue of SPILLAN EIENDOM AS?

SPILLAN EIENDOM AS had revenue of NOK 341,000 in 2024.

Where is SPILLAN EIENDOM AS based?

SPILLAN EIENDOM AS has its business address in Bergen.

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.