BIZTRAC BETA
Rental and operating of own or leased real estate

SWAN EIENDOM AS

Org. no. 923320555 Limited company (AS) Trondheim Incorporated 2019 Active
Ownership graph ↗
Revenue 2024 NOK 6.6m
Operating profit NOK 4.6m
Equity NOK 8.1m
Incorporated 2019
Share capital NOK 170,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

SWAN EIENDOM AS is registered as a limited company in Trondheim, Trøndelag with organisation number 923320555. 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 170,000, divided into 100 shares. The company's stated purpose is: “Utvikling, drift og utleie av eiendom samt relaterte tjenester og investering i aksjer.”. The most recent filed accounts, for the 2024 financial year, show NOK 6.6m in revenue and NOK 4.6m in operating profit.

Key figures · 2024

Revenue
NOK 6.6m
Operating profit
NOK 4.6m
Equity
NOK 8.1m
Est. value
NOK 12.4m

Financial health · 2024

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

Who owns SWAN EIENDOM AS?

FUNERALE AS
SWAN EIENDOM AS
NOK 6.6m rev. · NOK 4.6m profit

SWAN EIENDOM AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about SWAN EIENDOM AS

Who owns SWAN EIENDOM AS?

FUNERALE AS is the largest registered owner, with 51.0%.

What is the revenue of SWAN EIENDOM AS?

SWAN EIENDOM AS had revenue of NOK 6.6m in 2024.

Who is the general manager of SWAN EIENDOM AS?

Lars Erik Svanholm is registered as general manager of SWAN EIENDOM AS.

Where is SWAN EIENDOM AS based?

SWAN EIENDOM AS has its business address in Trondheim.

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.