BIZTRAC BETA
Rental and operating of own or leased real estate

PARADIS NÆRINGSEIENDOM AS

Org. no. 984364105 Limited company (AS) Bergen Incorporated 2002 Active
Ownership graph ↗
Revenue 2024 NOK 6.2m
Operating profit NOK 3.3m
Equity NOK 59.6m
Incorporated 2002
Share capital NOK 1.4m

Signals

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

PARADIS NÆRINGSEIENDOM AS is registered as a limited company in Bergen, Vestland with organisation number 984364105. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2002. Registered share capital is NOK 1.4m, divided into 482341 shares. The company's stated purpose is: “Investere i fast eiendom eller selskaper som eier fast eiendom, og alt som dermed står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 6.2m in revenue and NOK 3.3m in operating profit.

Key figures · 2024

Revenue
NOK 6.2m
Operating profit
NOK 3.3m
Equity
NOK 59.6m
Est. value
NOK 46.9m

Financial health · 2024

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

Who owns PARADIS NÆRINGSEIENDOM AS?

MIDGARD ALFA AS
PARADIS NÆRINGSEIENDOM AS
NOK 6.2m rev. · NOK 3.3m profit

PARADIS NÆRINGSEIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about PARADIS NÆRINGSEIENDOM AS

Who owns PARADIS NÆRINGSEIENDOM AS?

MIDGARD ALFA AS is the largest registered owner, with 100.0%.

What is the revenue of PARADIS NÆRINGSEIENDOM AS?

PARADIS NÆRINGSEIENDOM AS had revenue of NOK 6.2m in 2024.

Where is PARADIS NÆRINGSEIENDOM AS based?

PARADIS NÆRINGSEIENDOM 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.