BIZTRAC BETA
Buying and selling of own real estate

AURSKOG EIENDOMSINVEST AS

Org. no. 894818832 Limited company (AS) Aurskog-Høland Incorporated 2009 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −36,000
Equity NOK 2.2m
Incorporated 2009
Share capital NOK 3.2m

Signals

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

AURSKOG EIENDOMSINVEST AS is registered as a limited company in Aurskog-Høland, Akershus with organisation number 894818832. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2009. Registered share capital is NOK 3.2m, divided into 100 shares. The company's stated purpose is: “Investere i fast eiendom, med tilhørende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −36,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −36,000
Equity
NOK 2.2m
Est. value
NOK 2.0m

Financial health · 2025

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

Who owns AURSKOG EIENDOMSINVEST AS?

AURSKOG SPAREBANK
AURSKOG EIENDOMSINVEST AS
NOK 0 rev. · NOK −36,000 profit

AURSKOG EIENDOMSINVEST AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about AURSKOG EIENDOMSINVEST AS

Who owns AURSKOG EIENDOMSINVEST AS?

AURSKOG SPAREBANK is the largest registered owner, with 100.0%.

What is the revenue of AURSKOG EIENDOMSINVEST AS?

AURSKOG EIENDOMSINVEST AS had revenue of NOK 0 in 2025.

Where is AURSKOG EIENDOMSINVEST AS based?

AURSKOG EIENDOMSINVEST AS has its business address in Aurskog.

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.