BIZTRAC BETA
Rental and operating of own or leased real estate

B-NOM EIENDOM AS

Org. no. 992121858 Limited company (AS) Vefsn Incorporated 2007 Active
Ownership graph ↗
Revenue 2025 NOK 540,000
Operating profit NOK 302,000
Equity NOK 494,000
Incorporated 2007
Share capital NOK 100,000

B-NOM EIENDOM AS is registered as a limited company in Vefsn, Nordland with organisation number 992121858. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2007. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Eie og leie ut fast eiendom, og drive varehandel innen sportsartikler, samt det som har naturlig tilknytning til dette, herunder å delta i andre selskaper med lignende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 540,000 in revenue and NOK 302,000 in operating profit.

Key figures · 2025

Revenue
NOK 540,000
Operating profit
NOK 302,000
Equity
NOK 494,000
Est. value
NOK 597,000

Financial health · 2025

Liquidity
51.42
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
8.1%
Weak
Equity as a share of total capital

Who owns B-NOM EIENDOM AS?

BRITT NINA STORENG FORSMO
B-NOM EIENDOM AS
NOK 540,000 rev. · NOK 302,000 profit

B-NOM EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about B-NOM EIENDOM AS

Who owns B-NOM EIENDOM AS?

BRITT NINA STORENG FORSMO is the largest registered owner, with 100.0%.

What is the revenue of B-NOM EIENDOM AS?

B-NOM EIENDOM AS had revenue of NOK 540,000 in 2025.

Who is the general manager of B-NOM EIENDOM AS?

Britt Nina Storeng Forsmo is registered as general manager of B-NOM EIENDOM AS.

Where is B-NOM EIENDOM AS based?

B-NOM EIENDOM AS has its business address in Mosjøen.

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.