BIZTRAC BETA
Rental and operating of own or leased real estate

LJABRUBAKKEN 1 AS

Org. no. 986723056 Limited company (AS) Gjøvik Incorporated 2004 Active
Ownership graph ↗
Revenue 2024 NOK 1.4m
Operating profit NOK 621,000
Equity NOK 1.5m
Incorporated 2004
Share capital NOK 100,000

Signals

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

LJABRUBAKKEN 1 AS is registered as a limited company in Gjøvik, Innlandet with organisation number 986723056. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2004. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Eie fast eiendom eller aksjer i selskaper som eier fast eiendom, utvikle, omsette, leie ut og for øvrig administrere fast eiendom, samt hva som dermed står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.4m in revenue and NOK 621,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.4m
Operating profit
NOK 621,000
Equity
NOK 1.5m
Est. value
NOK 2.2m

Financial health · 2024

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

Who owns LJABRUBAKKEN 1 AS?

MIRAMARE CAPITAL AS
LJABRUBAKKEN 1 AS
NOK 1.4m rev. · NOK 621,000 profit

LJABRUBAKKEN 1 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LJABRUBAKKEN 1 AS

Who owns LJABRUBAKKEN 1 AS?

MIRAMARE CAPITAL AS is the largest registered owner, with 100.0%.

What is the revenue of LJABRUBAKKEN 1 AS?

LJABRUBAKKEN 1 AS had revenue of NOK 1.4m in 2024.

Where is LJABRUBAKKEN 1 AS based?

LJABRUBAKKEN 1 AS has its business address in Biri.

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.