BIZTRAC BETA
COMPANY REGISTER PROFILE
927346036 ORG. NO. 2022 ACCOUNTS 7 SECTIONS
Bankrupt UPDATED 02.09.2026
NAVLE EIENDOM AS is registered as “Bankrupt” with the Brønnøysund Register Centre.
Development of building projects

NAVLE EIENDOM AS

Org. no. 927346036 Limited company (AS) Stange Incorporated 2021 Bankrupt
Ownership graph ↗
Revenue 2022 NOK 31.5m
Operating profit NOK 1.3m
Equity NOK 244,000
Incorporated 2021
Share capital NOK 30,000

Signals

2 flags
  • Konkurs Selskapet er registrert konkurs i Enhetsregisteret.
  • Utdatert regnskap Siste registrerte regnskap er fra 2022.

NAVLE EIENDOM AS is registered as a limited company in Stange, Innlandet with organisation number 927346036. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Kjøpe, utvikle, drifte og evt. selge eiendom, samt å yte tekniske konsulenttjenester, drive agentur og handel, produksjon av forskjellige varer, tjenester, transport og lagervirksomhet mm.”. The most recent filed accounts, for the 2022 financial year, show NOK 31.5m in revenue and NOK 1.3m in operating profit.

Key figures · 2022

Revenue
NOK 31.5m
Operating profit
NOK 1.3m
Equity
NOK 244,000

Financial health · 2022

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

Who owns NAVLE EIENDOM AS?

No shareholders are registered for NAVLE EIENDOM AS in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about NAVLE EIENDOM AS

What is the revenue of NAVLE EIENDOM AS?

NAVLE EIENDOM AS had revenue of NOK 31.5m in 2022.

Where is NAVLE EIENDOM AS based?

NAVLE EIENDOM AS has its business address in Ottestad.

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.