BIZTRAC BETA
Intermediation service activities for non-specialised retail sale

TINE ULVESETH AS

Org. no. 924924721 Limited company (AS) Øygarden Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 65,000
Operating profit NOK 22,000
Equity NOK 30,000
Incorporated 2020
Share capital NOK 30,000

TINE ULVESETH AS is registered as a limited company in Øygarden, Vestland with organisation number 924924721. The business is classified under intermediation service activities for non-specialised retail sale (NACE 47.910). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Direktesalg eteriske oljer. Undervisning i naturlig livsstil og det som hører under dette. Investering i aksjer og andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 65,000 in revenue and NOK 22,000 in operating profit.

Key figures · 2025

Revenue
NOK 65,000
Operating profit
NOK 22,000
Equity
NOK 30,000
Est. value
NOK 88,000

Financial health · 2025

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

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

Who owns TINE ULVESETH AS?

TINE ULVESETH
TINE ULVESETH AS
NOK 65,000 rev. · NOK 22,000 profit

TINE ULVESETH AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TINE ULVESETH AS

Who owns TINE ULVESETH AS?

TINE ULVESETH is the largest registered owner, with 100.0%.

What is the revenue of TINE ULVESETH AS?

TINE ULVESETH AS had revenue of NOK 65,000 in 2025.

Who is the general manager of TINE ULVESETH AS?

Tine Ulveseth is registered as general manager of TINE ULVESETH AS.

Where is TINE ULVESETH AS based?

TINE ULVESETH AS has its business address in Fjell.

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.