biztrac. BETA
COMPANY REGISTER PROFILE
989073486 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Retail sale of hardware, building materials, paints and glass

EIEBAKKE AS

Org. no. 989073486 Limited company (AS) Indre Østfold Incorporated 2005 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −45,000
Equity NOK 889,000
Incorporated 2005
Share capital NOK 200,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−45k kr).

EIEBAKKE AS is registered as a limited company in Indre Østfold, Østfold with organisation number 989073486. The business is classified under retail sale of hardware, building materials, paints and glass (NACE 47.520). The company was incorporated in 2005. Registered share capital is NOK 200,000, divided into 200 shares. The company's stated purpose is: “Eie og investere i aksjer og eiendom mv., samt handel og konsulentvirksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −45,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −45,000
▼ −15 %
Equity
NOK 889,000
▼ −2 %
Est. value
NOK 1.1m

Financial health · 2025

Liquidity
22.92
Very good
Current assets ÷ current liabilities
Profitability
1.3%
Weak
Return on total assets
Solidity
15.2%
Satisfactory
Equity as a share of total capital

Who owns EIEBAKKE AS?

EIEBAKKE AS
NOK 0 rev. · NOK −45,000 profit

EIEBAKKE AS has 1 registered shareholder:

All shareholders and roles →

Which companies does EIEBAKKE AS own?

EIEBAKKE AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about EIEBAKKE AS

Who owns EIEBAKKE AS?

Fredrik Haugen is the largest registered owner, with 100.0%.

What is the revenue of EIEBAKKE AS?

EIEBAKKE AS had revenue of NOK 0 in 2025.

Where is EIEBAKKE AS based?

EIEBAKKE AS has its business address in Askim.

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

Report a problem

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