BIZTRAC BETA
Development of building projects

LØVÅSBAKKEN AS

Org. no. 914769728 Limited company (AS) Trysil Incorporated 2014 Active
Ownership graph ↗
Revenue 2024 NOK 2.0m
Operating profit NOK 1.8m
Equity NOK 5.1m
Incorporated 2014
Share capital NOK 30,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

LØVÅSBAKKEN AS is registered as a limited company in Trysil, Innlandet with organisation number 914769728. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2014. Registered share capital is NOK 30,000, divided into 2000 shares. The company's stated purpose is: “Drive utvikling av eiendom, salg og markedsføring av, herunder også oppføring av bygninger på disse. Videre kjøp av fast eiendom, investering i fast eiendom og aksjer.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.0m in revenue and NOK 1.8m in operating profit.

Key figures · 2024

Revenue
NOK 2.0m
Operating profit
NOK 1.8m
Equity
NOK 5.1m
Est. value
NOK 7.0m

Financial health · 2024

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

Who owns LØVÅSBAKKEN AS?

FUNDUS AS
LØVÅSBAKKEN AS
NOK 2.0m rev. · NOK 1.8m profit

LØVÅSBAKKEN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LØVÅSBAKKEN AS

Who owns LØVÅSBAKKEN AS?

FUNDUS AS is the largest registered owner, with 100.0%.

What is the revenue of LØVÅSBAKKEN AS?

LØVÅSBAKKEN AS had revenue of NOK 2.0m in 2024.

Who is the general manager of LØVÅSBAKKEN AS?

Håkan Stengrundet is registered as general manager of LØVÅSBAKKEN AS.

Where is LØVÅSBAKKEN AS based?

LØVÅSBAKKEN AS has its business address in Trysil.

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.