BIZTRAC BETA
Wholesale of coffee, tea, cocoa and spices

UNIBRAND AS

Org. no. 979946880 Limited company (AS) Arendal Incorporated 1998 Active
Ownership graph ↗
Revenue 2024 NOK 12.3m
Operating profit NOK 683,000
Equity NOK 1.1m
Incorporated 1998
Employees 12
Share capital NOK 300,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

UNIBRAND AS is registered as a limited company in Arendal, Agder with organisation number 979946880. The business is classified under wholesale of coffee, tea, cocoa and spices (NACE 46.370). The company was incorporated in 1998 and has 12 registered employees. Registered share capital is NOK 300,000, divided into 1000 shares. The company's stated purpose is: “Salg, markedsføring og teknisk vedlikehold av kaffe- og vannmaskiner med tilbehør, samt deltakelse i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 12.3m in revenue and NOK 683,000 in operating profit.

Key figures · 2024

Revenue
NOK 12.3m
Operating profit
NOK 683,000
Equity
NOK 1.1m
Est. value
NOK 3.2m

Financial health · 2024

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

Who owns UNIBRAND AS?

KONTOR HOLDING AS
UNIBRAND AS
NOK 12.3m rev. · NOK 683,000 profit

UNIBRAND AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about UNIBRAND AS

Who owns UNIBRAND AS?

KONTOR HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of UNIBRAND AS?

UNIBRAND AS had revenue of NOK 12.3m in 2024.

Who is the general manager of UNIBRAND AS?

Trond Johan Østereng is registered as general manager of UNIBRAND AS.

Where is UNIBRAND AS based?

UNIBRAND AS has its business address in Arendal.

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.