BIZTRAC BETA
COMPANY REGISTER PROFILE
920239595 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Rental and operating of own or leased real estate

ØRSNESALLEEN EIENDOM AS

Org. no. 920239595 Limited company (AS) Tønsberg Incorporated 2018 Active
Ownership graph ↗
Operating profit NOK −45,000
Equity NOK 468,000
Incorporated 2018
Share capital NOK 500,000

Signals

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

ØRSNESALLEEN EIENDOM AS is registered as a limited company in Tønsberg, Vestfold with organisation number 920239595. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2018. Registered share capital is NOK 500,000, divided into 500 shares. The company's stated purpose is: “Investering i, utvikling av og utleie av fast eiendom, samt deltakelse i andre virksomheter.”.

Key figures · 2025

Operating profit
NOK −45,000
▼ −120 %
Equity
NOK 468,000
▼ −6 %
Est. value
NOK 414,000

Financial health · 2025

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

Who owns ØRSNESALLEEN EIENDOM AS?

ØRSNESALLEEN EIENDOM AS
· NOK −45,000 profit

ØRSNESALLEEN EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ØRSNESALLEEN EIENDOM AS

Who owns ØRSNESALLEEN EIENDOM AS?

ZEINER BOLIG AS is the largest registered owner, with 100.0%.

Who is the general manager of ØRSNESALLEEN EIENDOM AS?

Johan Lauritz Zeiner is registered as general manager of ØRSNESALLEEN EIENDOM AS.

Where is ØRSNESALLEEN EIENDOM AS based?

ØRSNESALLEEN EIENDOM AS has its business address in Tønsberg.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 02.09.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.