BIZTRAC BETA
COMPANY REGISTER PROFILE
914391814 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Other real estate activities on a fee or contract basis

LUNDE BÅTBYGGERI AS

Org. no. 914391814 Limited company (AS) Tysnes Incorporated 2014 Active
Ownership graph ↗
Revenue 2025 NOK 242,000
Operating profit NOK 89,000
Equity NOK −1.9m
Incorporated 2014
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−1,9 mill kr).

LUNDE BÅTBYGGERI AS is registered as a limited company in Tysnes, Vestland with organisation number 914391814. The business is classified under other real estate activities on a fee or contract basis (NACE 68.320). The company was incorporated in 2014. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Forvalte og leie ut næringseiendom, samt utvikle eiendom, i tillegg til verkstedsvirksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 242,000 in revenue and NOK 89,000 in operating profit.

Key figures · 2025

Revenue
NOK 242,000
▲ +32 %
Operating profit
NOK 89,000
▲ +8 %
Equity
NOK −1.9m
▼ −0 %
Est. value
NOK 631,000

Financial health · 2025

Liquidity
0.07
Not satisfactory
Current assets ÷ current liabilities
Profitability
43.2%
Very good
Return on total assets
Solidity
-1064.4%
Weak
Equity as a share of total capital

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

Who owns LUNDE BÅTBYGGERI AS?

LUNDE BÅTBYGGERI AS has 5 registered shareholders:

All shareholders and roles →

Frequently asked questions about LUNDE BÅTBYGGERI AS

Who owns LUNDE BÅTBYGGERI AS?

JARLE BELT is the largest registered owner, with 20.0%.

What is the revenue of LUNDE BÅTBYGGERI AS?

LUNDE BÅTBYGGERI AS had revenue of NOK 242,000 in 2025.

Where is LUNDE BÅTBYGGERI AS based?

LUNDE BÅTBYGGERI AS has its business address in Lundegrend.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 02.09.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.