biztrac. BETA
COMPANY REGISTER PROFILE
942471386 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Rental and operating of own or leased real estate

BJF EIENDOM AS

Org. no. 942471386 Limited company (AS) Gjøvik Incorporated 1987 Active
Ownership graph ↗
Revenue 2025 NOK 3.1m
Operating profit NOK 1.9m
Equity NOK 15.7m
Incorporated 1987
Share capital NOK 356,000

BJF EIENDOM AS is registered as a limited company in Gjøvik, Innlandet with organisation number 942471386. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1987. Registered share capital is NOK 356,000, divided into 178 shares. The company's stated purpose is: “Selskapets formål er å eie og leie ut fast eiendom samt det som står i forbindelse med dette og annen næringsvirksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.1m in revenue and NOK 1.9m in operating profit.

Former names: BIRI TRAFIKKSENTER AS, BIRI TRAFIKKSENTER EIENDOM AS

Key figures · 2025

Revenue
NOK 3.1m
▲ +16 %
Operating profit
NOK 1.9m
▲ +38 %
Equity
NOK 15.7m
▲ +4 %
Est. value
NOK 14.4m

Financial health · 2025

Liquidity
4.34
Very good
Current assets ÷ current liabilities
Profitability
7.5%
Satisfactory
Return on total assets
Solidity
55.1%
Very good
Equity as a share of total capital

Who owns BJF EIENDOM AS?

BJF EIENDOM AS has 4 registered shareholders:

All shareholders and roles →

Frequently asked questions about BJF EIENDOM AS

Who owns BJF EIENDOM AS?

Bjørn Feiring is the largest registered owner, with 25.8%.

What is the revenue of BJF EIENDOM AS?

BJF EIENDOM AS had revenue of NOK 3.1m in 2025.

Who is the general manager of BJF EIENDOM AS?

Pål Kristian Feiring is registered as general manager of BJF EIENDOM AS.

Where is BJF EIENDOM AS based?

BJF EIENDOM 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 03.10.2026.

Report a problem

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