BIZTRAC BETA
Uoppgitt

LB TELLNES AS

Org. no. 928778754 Limited company (AS) Øygarden Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 48,000
Operating profit NOK 48,000
Equity NOK 279,000
Incorporated 2022
Share capital NOK 30,000

LB TELLNES AS is registered as a limited company in Øygarden, Vestland with organisation number 928778754. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Skaffe aksjeeierne utbytte ved konsulentvirksomhet, undervisning, investering i andre selskaper og hva dermed står forbindelse, investering i eiendom og handel.”. The most recent filed accounts, for the 2025 financial year, show NOK 48,000 in revenue and NOK 48,000 in operating profit.

Key figures · 2025

Revenue
NOK 48,000
Operating profit
NOK 48,000
Equity
NOK 279,000
Est. value
NOK 280,000

Financial health · 2025

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

Who owns LB TELLNES AS?

LINN BEATE HOMLEID TELLNES
LB TELLNES AS
NOK 48,000 rev. · NOK 48,000 profit

LB TELLNES AS has 1 registered shareholder:

All shareholders and roles →

Which companies does LB TELLNES AS own?

LB TELLNES AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about LB TELLNES AS

Who owns LB TELLNES AS?

LINN BEATE HOMLEID TELLNES is the largest registered owner, with 100.0%.

What is the revenue of LB TELLNES AS?

LB TELLNES AS had revenue of NOK 48,000 in 2025.

Who is the general manager of LB TELLNES AS?

Linn Beate Homleid Tellnes is registered as general manager of LB TELLNES AS.

Where is LB TELLNES AS based?

LB TELLNES AS has its business address in Knarrevik.

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.