BIZTRAC BETA
Rental and operating of own or leased real estate

BJØRNS BYGG EIENDOM AS

Org. no. 931278010 Limited company (AS) Tønsberg Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 600,000
Operating profit NOK 353,000
Equity NOK 738,000
Incorporated 2023
Share capital NOK 500,000

BJØRNS BYGG EIENDOM AS is registered as a limited company in Tønsberg, Vestfold with organisation number 931278010. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2023. Registered share capital is NOK 500,000, divided into 500000 shares. The company's stated purpose is: “Investering i eiendom samt annen investeringsvirksomhet og hva dermed står i forbindelse herunder å delta i andre selskaper med lignende virksomhet, kjøp og salg av aksjer, eller på annen måte gjøre seg interessert i andre foretagender.”. The most recent filed accounts, for the 2025 financial year, show NOK 600,000 in revenue and NOK 353,000 in operating profit.

Key figures · 2025

Revenue
NOK 600,000
Operating profit
NOK 353,000
Equity
NOK 738,000
Est. value
NOK 1.1m

Financial health · 2025

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

Who owns BJØRNS BYGG EIENDOM AS?

BJØRNS BYGG AS
BJØRNS BYGG EIENDOM AS
NOK 600,000 rev. · NOK 353,000 profit

BJØRNS BYGG EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BJØRNS BYGG EIENDOM AS

Who owns BJØRNS BYGG EIENDOM AS?

BJØRNS BYGG AS is the largest registered owner, with 100.0%.

What is the revenue of BJØRNS BYGG EIENDOM AS?

BJØRNS BYGG EIENDOM AS had revenue of NOK 600,000 in 2025.

Where is BJØRNS BYGG EIENDOM AS based?

BJØRNS BYGG EIENDOM AS has its business address in Revetal.

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.