BIZTRAC BETA
Rental and operating of own or leased real estate

NYE HJEM BJØRNEGÅRDSVINGEN 11-13 AS

Org. no. 890844782 Limited company (AS) Oslo Incorporated 2007 Active
Ownership graph ↗
Operating profit NOK −60,000
Equity NOK 665,000
Incorporated 2007
Share capital NOK 100,000

Signals

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

NYE HJEM BJØRNEGÅRDSVINGEN 11-13 AS is registered as a limited company in Oslo, Oslo with organisation number 890844782. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2007. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Kjøp, salg, utleie og utvikling av fast eiendom samt hva hermed står i forbindelse, herunder deltagelse i andre selskaper med lignende virksomhet.”.

Key figures · 2024

Operating profit
NOK −60,000
Equity
NOK 665,000
Est. value
NOK 2.8m

Financial health · 2024

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

Who owns NYE HJEM BJØRNEGÅRDSVINGEN 11-13 AS?

OBOS NYE HJEM AS
NYE HJEM BJØRNEGÅRDSVINGEN 11-13 AS
· NOK −60,000 profit

NYE HJEM BJØRNEGÅRDSVINGEN 11-13 AS has 1 registered shareholder:

All shareholders and roles →

Group structure

NYE HJEM BJØRNEGÅRDSVINGEN 11-13 AS er morselskap for 67 datterselskaper:

Frequently asked questions about NYE HJEM BJØRNEGÅRDSVINGEN 11-13 AS

Who owns NYE HJEM BJØRNEGÅRDSVINGEN 11-13 AS?

OBOS NYE HJEM AS is the largest registered owner, with 100.0%.

Where is NYE HJEM BJØRNEGÅRDSVINGEN 11-13 AS based?

NYE HJEM BJØRNEGÅRDSVINGEN 11-13 AS has its business address in Oslo.

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.