BIZTRAC BETA
Non-specialised retail sale of predominately food, beverages or tobacco

ENGENES DAGLIGVARE AS

Org. no. 990006784 Limited company (AS) Ibestad Incorporated 2006 Active
Ownership graph ↗
Revenue 2024 NOK 6.6m
Operating profit NOK 57,000
Equity NOK 1.4m
Incorporated 2006
Employees 5
Share capital NOK 403,000

ENGENES DAGLIGVARE AS is registered as a limited company in Ibestad, Troms with organisation number 990006784. The business is classified under non-specialised retail sale of predominately food, beverages or tobacco (NACE 47.110). The company was incorporated in 2006 and has 5 registered employees. Registered share capital is NOK 403,000, divided into 1000 shares. The company's stated purpose is: “Butikkhandel med bredt vareutvalg samt deltakelse i selskaper med økonomisk formål.”. The most recent filed accounts, for the 2024 financial year, show NOK 6.6m in revenue and NOK 57,000 in operating profit.

Key figures · 2024

Revenue
NOK 6.6m
Operating profit
NOK 57,000
Equity
NOK 1.4m
Est. value
NOK 906,000

Financial health · 2024

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

Who owns ENGENES DAGLIGVARE AS?

TROND JENSEN
ENGENES DAGLIGVARE AS
NOK 6.6m rev. · NOK 57,000 profit

ENGENES DAGLIGVARE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ENGENES DAGLIGVARE AS

Who owns ENGENES DAGLIGVARE AS?

TROND JENSEN is the largest registered owner, with 100.0%.

What is the revenue of ENGENES DAGLIGVARE AS?

ENGENES DAGLIGVARE AS had revenue of NOK 6.6m in 2024.

Who is the general manager of ENGENES DAGLIGVARE AS?

Trond Jensen is registered as general manager of ENGENES DAGLIGVARE AS.

Where is ENGENES DAGLIGVARE AS based?

ENGENES DAGLIGVARE AS has its business address in Engenes.

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.