BIZTRAC BETA
Restaurant activities

LADEGÅRDEN KRO AS

Org. no. 931225065 Limited company (AS) Nittedal Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 2.1m
Operating profit NOK −286,000
Equity NOK 647,000
Incorporated 2023
Share capital NOK 30,000

Signals

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

LADEGÅRDEN KRO AS is registered as a limited company in Nittedal, Akershus with organisation number 931225065. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Drive restaurant, kafé og annen cateringvirksomhet, samt hva hermed står i forbindelse, herunder deltagelse i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.1m in revenue and NOK −286,000 in operating profit.

Key figures · 2024

Revenue
NOK 2.1m
Operating profit
NOK −286,000
Equity
NOK 647,000
Est. value
NOK 1.8m

Financial health · 2024

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

Who owns LADEGÅRDEN KRO AS?

MORTENS KRO AS
LADEGÅRDEN KRO AS
NOK 2.1m rev. · NOK −286,000 profit

LADEGÅRDEN KRO AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LADEGÅRDEN KRO AS

Who owns LADEGÅRDEN KRO AS?

MORTENS KRO AS is the largest registered owner, with 100.0%.

What is the revenue of LADEGÅRDEN KRO AS?

LADEGÅRDEN KRO AS had revenue of NOK 2.1m in 2024.

Who is the general manager of LADEGÅRDEN KRO AS?

Johnny Gereon Kristiansen is registered as general manager of LADEGÅRDEN KRO AS.

Where is LADEGÅRDEN KRO AS based?

LADEGÅRDEN KRO AS has its business address in Hagan.

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.