BIZTRAC BETA
Restaurant activities

TRETTENKRO AS

Org. no. 813884062 Limited company (AS) Øyer Incorporated 2014 Active
Ownership graph ↗
Revenue 2025 NOK 194,000
Operating profit NOK −853,000
Equity NOK 2.1m
Incorporated 2014
Share capital NOK 1.0m

Signals

2 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−853k kr).
  • Nylig endring 2026-02-12 Adresseendring registrert 2026-02-12.

TRETTENKRO AS is registered as a limited company in Øyer, Innlandet with organisation number 813884062. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 2014. Registered share capital is NOK 1.0m, divided into 30000 shares. The company's stated purpose is: “Å drive gjestgiveri og campingvirksomhet og annen virksomhet som naturlig faller inn under dette, samt øvrig forretningsvirksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 194,000 in revenue and NOK −853,000 in operating profit.

Key figures · 2025

Revenue
NOK 194,000
Operating profit
NOK −853,000
Equity
NOK 2.1m
Est. value
NOK 1.1m

Financial health · 2025

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

Who owns TRETTENKRO AS?

CHANPRADAB FJELDSTAD
TRETTENKRO AS
NOK 194,000 rev. · NOK −853,000 profit

TRETTENKRO AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TRETTENKRO AS

Who owns TRETTENKRO AS?

CHANPRADAB FJELDSTAD is the largest registered owner, with 100.0%.

What is the revenue of TRETTENKRO AS?

TRETTENKRO AS had revenue of NOK 194,000 in 2025.

Who is the general manager of TRETTENKRO AS?

Egil Fjeldstad is registered as general manager of TRETTENKRO AS.

Where is TRETTENKRO AS based?

TRETTENKRO AS has its business address in Tretten.

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.