BIZTRAC BETA
Rental and operating of own or leased real estate

LERFLATEN GÅRD AS

Org. no. 929049314 Limited company (AS) Trondheim Incorporated 2022 Active
Ownership graph ↗
Revenue 2024 NOK 2.2m
Operating profit NOK 252,000
Equity NOK 330,000
Incorporated 2022
Employees 6
Share capital NOK 30,000

LERFLATEN GÅRD AS is registered as a limited company in Trondheim, Trøndelag with organisation number 929049314. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2022 and has 6 registered employees. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Drift av serveringsvirksomhet, utleie av lokaler, gårdsopplevelser og kulturarrangementer, samt annen virksomhet relatert gården og gårdens ressurser.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.2m in revenue and NOK 252,000 in operating profit.

Key figures · 2024

Revenue
NOK 2.2m
Operating profit
NOK 252,000
Equity
NOK 330,000
Est. value
NOK 838,000

Financial health · 2024

Liquidity
1.09
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
28.9%
Good
Equity as a share of total capital

Who owns LERFLATEN GÅRD AS?

GRO HELENE LERFLATEN
LERFLATEN GÅRD AS
NOK 2.2m rev. · NOK 252,000 profit

LERFLATEN GÅRD AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about LERFLATEN GÅRD AS

Who owns LERFLATEN GÅRD AS?

GRO HELENE LERFLATEN is the largest registered owner, with 50.0%.

What is the revenue of LERFLATEN GÅRD AS?

LERFLATEN GÅRD AS had revenue of NOK 2.2m in 2024.

Who is the general manager of LERFLATEN GÅRD AS?

Gro Helene Lerflaten is registered as general manager of LERFLATEN GÅRD AS.

Where is LERFLATEN GÅRD AS based?

LERFLATEN GÅRD 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 15.06.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.