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

BEFF EIENDOM AS

Org. no. 998896959 Limited company (AS) Skien Incorporated 2012 Active
Revenue 2025 NOK 600,000
Operating profit NOK 332,000
Equity NOK 2.4m
Incorporated 2012
Share capital NOK 800,000

BEFF EIENDOM AS is registered as a limited company in Skien, Telemark with organisation number 998896959. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2012. Registered share capital is NOK 800,000, divided into 800 shares. The company's stated purpose is: “Kjøp, salg og utleie av fast eiendom, samt investeringer i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 600,000 in revenue and NOK 332,000 in operating profit.

Key figures · 2025

Revenue
NOK 600,000
▲ +0 %
Operating profit
NOK 332,000
▼ −29 %
Equity
NOK 2.4m
▲ +12 %
Est. value
NOK 2.6m

Financial health · 2025

Liquidity
2.67
Very good
Current assets ÷ current liabilities
Profitability
12.4%
Good
Return on total assets
Solidity
88.5%
Very good
Equity as a share of total capital

Who owns BEFF EIENDOM AS?

BEFF EIENDOM AS
NOK 600,000 rev. · NOK 332,000 profit

BEFF EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Group structure

BEFF EIENDOM AS er morselskap for 2 datterselskaper:

Frequently asked questions about BEFF EIENDOM AS

Who owns BEFF EIENDOM AS?

BERGAN HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of BEFF EIENDOM AS?

BEFF EIENDOM AS had revenue of NOK 600,000 in 2025.

Who is the general manager of BEFF EIENDOM AS?

Helge Bergan is registered as general manager of BEFF EIENDOM AS.

Where is BEFF EIENDOM AS based?

BEFF EIENDOM AS has its business address in Skien.

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.