biztrac. BETA
COMPANY REGISTER PROFILE
984207824 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Restaurant activities

ESTENSTAD DRIFT AS

Org. no. 984207824 Limited company (AS) Trondheim Incorporated 2002 Active
Revenue 2025 NOK 6.3m
Operating profit NOK 73,000
Equity NOK 951,000
Incorporated 2002
Employees 11
Share capital NOK 100,000

ESTENSTAD DRIFT AS is registered as a limited company in Trondheim, Trøndelag with organisation number 984207824. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 2002 and has 11 registered employees. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Produksjonskjøkken, serveringsvirksomhet og beslektet virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 6.3m in revenue and NOK 73,000 in operating profit.

Former names: LADE KAFE & GRILL AS

Key figures · 2025

Revenue
NOK 6.3m
▲ +12 %
Operating profit
NOK 73,000
▼ −47 %
Equity
NOK 951,000
▲ +6 %
Est. value
NOK 858,000

Financial health · 2025

Liquidity
1.40
Satisfactory
Current assets ÷ current liabilities
Profitability
4.5%
Weak
Return on total assets
Solidity
59.2%
Very good
Equity as a share of total capital

Who owns ESTENSTAD DRIFT AS?

ESTENSTAD DRIFT AS
NOK 6.3m rev. · NOK 73,000 profit

ESTENSTAD DRIFT AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ESTENSTAD DRIFT AS

Who owns ESTENSTAD DRIFT AS?

Jarl Inge Krognes is the largest registered owner, with 100.0%.

What is the revenue of ESTENSTAD DRIFT AS?

ESTENSTAD DRIFT AS had revenue of NOK 6.3m in 2025.

Who is the general manager of ESTENSTAD DRIFT AS?

Jarl Inge Krognes is registered as general manager of ESTENSTAD DRIFT AS.

Where is ESTENSTAD DRIFT AS based?

ESTENSTAD DRIFT AS has its business address in Trondheim.

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.