BIZTRAC BETA
Rental and operating of own or leased real estate

BJØRNLIA AS

Org. no. 981942477 Limited company (AS) Elverum Incorporated 2000 Active
Ownership graph ↗
Revenue 2025 NOK 783,000
Operating profit NOK 349,000
Equity NOK −1.3m
Incorporated 2000
Share capital NOK 100,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−1,3 mill kr).

BJØRNLIA AS is registered as a limited company in Elverum, Innlandet with organisation number 981942477. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2000. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Utbygging og utleie av bolig- og fritidseiendom, herunder deltagelse i andre selskaper med samme eller lignende formål.”. The most recent filed accounts, for the 2025 financial year, show NOK 783,000 in revenue and NOK 349,000 in operating profit.

Key figures · 2025

Revenue
NOK 783,000
Operating profit
NOK 349,000
Equity
NOK −1.3m
Est. value
NOK 2.4m

Financial health · 2025

Liquidity
0.96
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-8.4%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns BJØRNLIA AS?

LEIF BJØRNAR MYHREN
BJØRNLIA AS
NOK 783,000 rev. · NOK 349,000 profit

BJØRNLIA AS has 1 registered shareholder:

All shareholders and roles →

Which companies does BJØRNLIA AS own?

BJØRNLIA AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about BJØRNLIA AS

Who owns BJØRNLIA AS?

LEIF BJØRNAR MYHREN is the largest registered owner, with 100.0%.

What is the revenue of BJØRNLIA AS?

BJØRNLIA AS had revenue of NOK 783,000 in 2025.

Where is BJØRNLIA AS based?

BJØRNLIA AS has its business address in Elverum.

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.