BIZTRAC BETA
COMPANY REGISTER PROFILE
959837902 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Uoppgitt

ØSTENFJELDSKE EIENDOM AS

Org. no. 959837902 Limited company (AS) Asker Incorporated 1990 Active
Ownership graph ↗
Equity NOK 820
Incorporated 1990
Share capital NOK 100,000

ØSTENFJELDSKE EIENDOM AS is registered as a limited company in Asker, Akershus with organisation number 959837902. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 1990. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Ervervelse, utvikling og omsetning av eiendom samt hva hermed står i forbindelse, herunder å delta i andre selskap med lignende formål.”.

Key figures · 2025

Equity
NOK 820
Est. value
NOK 964

Financial health · 2025

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

Solidity capped at Weak because equity is below NOK 100,000.

Who owns ØSTENFJELDSKE EIENDOM AS?

ØSTENFJELDSKE EIENDOM AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about ØSTENFJELDSKE EIENDOM AS

Who owns ØSTENFJELDSKE EIENDOM AS?

KNUT BLIKRA is the largest registered owner, with 71.0%.

Where is ØSTENFJELDSKE EIENDOM AS based?

ØSTENFJELDSKE EIENDOM AS has its business address in Spikkestad.

Property

Business address Spikkestadveien 147A, 3430 Spikkestad
Cadastral unit 3203-285/446/0/0
Building Annen boligbygning (sekundærbolig reindrift) · 4 units

4 companies are registered at this address.

The address this company is registered at, from the company register and matched against the cadastre. It does not say who owns the property — a company may be a tenant, and the address is often its accountant's. Source: Brønnøysundregistrene and © Kartverket.

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.