biztrac. BETA
COMPANY REGISTER PROFILE
991081674 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Other technical consultancy

COFFEE AS

Org. no. 991081674 Limited company (AS) Molde Incorporated 2007 Active
Operating profit NOK −69,000
Equity NOK 18.3m
Incorporated 2007
Share capital NOK 76,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−69k kr).

COFFEE AS is registered as a limited company in Molde, Møre og Romsdal with organisation number 991081674. The business is classified under other technical consultancy (NACE 71.129). The company was incorporated in 2007. Registered share capital is NOK 76,000, divided into 76 shares. The company's stated purpose is: “Holdingselskap med eierandeler i selskaper som driver med utvikling og produksjon innenfor materialteknologi, elektrokjemi, induksjon, sensorikk og utvikling av digitale flater.”.

Former names: TEKNOPARK MOLDE AS, TEKNOPARK MØRE AS, HUSTADVIKA HAVPARK AS, OBELL AS

Key figures · 2025

Operating profit
NOK −69,000
▼ −52 %
Equity
NOK 18.3m
▲ +38 %
Est. value
NOK 59.4m

Financial health · 2025

Liquidity
663.39
Very good
Current assets ÷ current liabilities
Profitability
20.6%
Very good
Return on total assets
Solidity
75.3%
Very good
Equity as a share of total capital

Who owns COFFEE AS?

COFFEE AS
· NOK −69,000 profit

COFFEE AS has 1 registered shareholder:

All shareholders and roles →

Which companies does COFFEE AS own?

COFFEE AS holds stakes in 5 companies:

See the full ownership structure →

Group structure

COFFEE AS er morselskap for 1 datterselskap:

Frequently asked questions about COFFEE AS

Who owns COFFEE AS?

OSHAUG AS is the largest registered owner, with 100.0%.

Who is the general manager of COFFEE AS?

Stein Berg Oshaug is registered as general manager of COFFEE AS.

Where is COFFEE AS based?

COFFEE AS has its business address in Molde.

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

Report a problem

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