BIZTRAC BETA
Business and other management consultancy activities

BEKKELUND EIENDOM AS

Org. no. 916334826 Limited company (AS) Nome Incorporated 2015 Active
Ownership graph ↗
Operating profit NOK −42,000
Equity NOK 2.4m
Incorporated 2015
Share capital NOK 2.3m

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−42k kr).

BEKKELUND EIENDOM AS is registered as a limited company in Nome, Telemark with organisation number 916334826. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2015. Registered share capital is NOK 2.3m, divided into 100 shares. The company's stated purpose is: “Konsulentarbeid, eie aksjer i andre selskap, investere i aksjer og andre verdipapirer, eie, utvikling, drift og utleie av fast eiendom, samt annen virksomhet som står i naturlig tilknytning til dette.”.

Key figures · 2025

Operating profit
NOK −42,000
Equity
NOK 2.4m
Est. value
NOK 5.4m

Financial health · 2025

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

Who owns BEKKELUND EIENDOM AS?

BJØRG TVEITO LUNDEFARET
BEKKELUND EIENDOM AS
· NOK −42,000 profit

BEKKELUND EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Which companies does BEKKELUND EIENDOM AS own?

BEKKELUND EIENDOM AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about BEKKELUND EIENDOM AS

Who owns BEKKELUND EIENDOM AS?

BJØRG TVEITO LUNDEFARET is the largest registered owner, with 100.0%.

Who is the general manager of BEKKELUND EIENDOM AS?

Bjørg Tveito Lundefaret is registered as general manager of BEKKELUND EIENDOM AS.

Where is BEKKELUND EIENDOM AS based?

BEKKELUND EIENDOM AS has its business address in Lunde.

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.