BIZTRAC BETA
Retail sale of household utensils, cutlery, crockery, glassware, tableware, china and pottery

EKB EIENDOM AS

Org. no. 987487534 Limited company (AS) Harstad Incorporated 2004 Active
Ownership graph ↗
Revenue 2024 NOK 623,000
Operating profit NOK 444,000
Equity NOK 1.1m
Incorporated 2004
Share capital NOK 100,000

EKB EIENDOM AS is registered as a limited company in Harstad, Troms with organisation number 987487534. The business is classified under retail sale of household utensils, cutlery, crockery, glassware, tableware, china and pottery (NACE 47.553). The company was incorporated in 2004. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Eiendomsselskap.”. The most recent filed accounts, for the 2024 financial year, show NOK 623,000 in revenue and NOK 444,000 in operating profit.

Key figures · 2024

Revenue
NOK 623,000
Operating profit
NOK 444,000
Equity
NOK 1.1m
Est. value
NOK 1.7m

Financial health · 2024

Liquidity
0.34
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
29.2%
Good
Equity as a share of total capital

Who owns EKB EIENDOM AS?

KNUT BENDIKSEN
EKB EIENDOM AS
NOK 623,000 rev. · NOK 444,000 profit

EKB EIENDOM AS has 2 registered shareholders:

All shareholders and roles →

Which companies does EKB EIENDOM AS own?

EKB EIENDOM AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about EKB EIENDOM AS

Who owns EKB EIENDOM AS?

KNUT BENDIKSEN is the largest registered owner, with 50.0%.

What is the revenue of EKB EIENDOM AS?

EKB EIENDOM AS had revenue of NOK 623,000 in 2024.

Who is the general manager of EKB EIENDOM AS?

Knut Bendiksen is registered as general manager of EKB EIENDOM AS.

Where is EKB EIENDOM AS based?

EKB EIENDOM AS has its business address in Harstad.

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.