BIZTRAC BETA
Restaurant activities

NAESS & LIHAUG AS

Org. no. 928342972 Limited company (AS) Oppdal Incorporated 2021 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −56,000
Equity NOK 846,000
Incorporated 2021
Share capital NOK 50,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−56k kr).

NAESS & LIHAUG AS is registered as a limited company in Oppdal, Trøndelag with organisation number 928342972. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 2021. Registered share capital is NOK 50,000, divided into 50000 shares. The company's stated purpose is: “Investeringsvirksomhet med aksjer og fast eiendom.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −56,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −56,000
Equity
NOK 846,000
Est. value
NOK 2.1m

Financial health · 2024

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

Who owns NAESS & LIHAUG AS?

TINA ELISE LIHAUG
NAESS & LIHAUG AS
NOK 0 rev. · NOK −56,000 profit

NAESS & LIHAUG AS has 2 registered shareholders:

All shareholders and roles →

Which companies does NAESS & LIHAUG AS own?

NAESS & LIHAUG AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about NAESS & LIHAUG AS

Who owns NAESS & LIHAUG AS?

TINA ELISE LIHAUG is the largest registered owner, with 52.0%.

What is the revenue of NAESS & LIHAUG AS?

NAESS & LIHAUG AS had revenue of NOK 0 in 2024.

Who is the general manager of NAESS & LIHAUG AS?

Tina Elise Lihaug is registered as general manager of NAESS & LIHAUG AS.

Where is NAESS & LIHAUG AS based?

NAESS & LIHAUG AS has its business address in Oppdal.

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.