BIZTRAC BETA
Other education activities

TELLUS WINE AS

Org. no. 918082271 Limited company (AS) Oslo Incorporated 2016 Active
Ownership graph ↗
Revenue 2025 NOK 1.2m
Operating profit NOK 240,000
Equity NOK 292,000
Incorporated 2016
Share capital NOK 30,000

TELLUS WINE AS is registered as a limited company in Oslo, Oslo with organisation number 918082271. The business is classified under other education activities (NACE 85.597). The company was incorporated in 2016. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Undervisning i fagene vin, italiensk kultur, reise, historie og gastronomi. Selskapet kan også tilby kurs- og foredragsvirksomhet og tilstøtende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.2m in revenue and NOK 240,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.2m
Operating profit
NOK 240,000
Equity
NOK 292,000
Est. value
NOK 1.1m

Financial health · 2024

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

Who owns TELLUS WINE AS?

LARS GEIR REIN-HELLIESEN
TELLUS WINE AS
NOK 1.2m rev. · NOK 240,000 profit

TELLUS WINE AS has 1 registered shareholder:

All shareholders and roles →

Which companies does TELLUS WINE AS own?

TELLUS WINE AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about TELLUS WINE AS

Who owns TELLUS WINE AS?

LARS GEIR REIN-HELLIESEN is the largest registered owner, with 100.0%.

What is the revenue of TELLUS WINE AS?

TELLUS WINE AS had revenue of NOK 1.2m in 2025.

Who is the general manager of TELLUS WINE AS?

Lars Geir Rein-Helliesen is registered as general manager of TELLUS WINE AS.

Where is TELLUS WINE AS based?

TELLUS WINE AS has its business address in Oslo.

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.