BIZTRAC BETA
Other technical consultancy

LUNDEBØ AS

Org. no. 920649882 Limited company (AS) Etne Incorporated 2018 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −8,000
Equity NOK 31,000
Incorporated 2018
Share capital NOK 50,000

Signals

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

LUNDEBØ AS is registered as a limited company in Etne, Vestland with organisation number 920649882. The business is classified under other technical consultancy (NACE 71.129). The company was incorporated in 2018. Registered share capital is NOK 50,000, divided into 50 shares. The company's stated purpose is: “Kjøp og salg av verdipapir, finansielle instrumenter samt alt som naturlig hører til dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −8,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −8,000
Equity
NOK 31,000
Est. value
NOK 51,000

Financial health · 2025

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

Solidity capped at Weak because equity is below NOK 100,000.

Who owns LUNDEBØ AS?

RUNE LUNDEBØ NESS
LUNDEBØ AS
NOK 0 rev. · NOK −8,000 profit

LUNDEBØ AS has 1 registered shareholder:

All shareholders and roles →

Which companies does LUNDEBØ AS own?

LUNDEBØ AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about LUNDEBØ AS

Who owns LUNDEBØ AS?

RUNE LUNDEBØ NESS is the largest registered owner, with 100.0%.

What is the revenue of LUNDEBØ AS?

LUNDEBØ AS had revenue of NOK 0 in 2025.

Who is the general manager of LUNDEBØ AS?

Rune Lundebø Ness is registered as general manager of LUNDEBØ AS.

Where is LUNDEBØ AS based?

LUNDEBØ AS has its business address in Etne.

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.