BIZTRAC BETA
Rental and operating of own or leased real estate

BJØRNEHIET EIENDOM AS

Org. no. 933019942 Limited company (AS) Senja Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 189,000
Operating profit NOK 146,000
Equity NOK 1.9m
Incorporated 2024
Share capital NOK 50,000

BJØRNEHIET EIENDOM AS is registered as a limited company in Senja, Troms with organisation number 933019942. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2024. Registered share capital is NOK 50,000, divided into 100 shares. The company's stated purpose is: “Investering i aksjer, verdipapirer, eiendomsprosjekter samt deltakelse i andre virksomheter og det som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 189,000 in revenue and NOK 146,000 in operating profit.

Key figures · 2025

Revenue
NOK 189,000
Operating profit
NOK 146,000
Equity
NOK 1.9m
Est. value
NOK 1.6m

Financial health · 2025

Liquidity
1.39
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
89.3%
Very good
Equity as a share of total capital

Who owns BJØRNEHIET EIENDOM AS?

R-P INVEST AS
BJØRNEHIET EIENDOM AS
NOK 189,000 rev. · NOK 146,000 profit

BJØRNEHIET EIENDOM AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about BJØRNEHIET EIENDOM AS

Who owns BJØRNEHIET EIENDOM AS?

R-P INVEST AS is the largest registered owner, with 50.0%.

What is the revenue of BJØRNEHIET EIENDOM AS?

BJØRNEHIET EIENDOM AS had revenue of NOK 189,000 in 2025.

Who is the general manager of BJØRNEHIET EIENDOM AS?

Roger Pedersen is registered as general manager of BJØRNEHIET EIENDOM AS.

Where is BJØRNEHIET EIENDOM AS based?

BJØRNEHIET EIENDOM AS has its business address in Finnsnes.

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.