BIZTRAC BETA
COMPANY REGISTER PROFILE
831189452 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Uoppgitt

HAPPYHOUR AS

Org. no. 831189452 Limited company (AS) Bærum Incorporated 2023 Active
Ownership graph ↗
Operating profit NOK −915
Equity NOK 22,000
Incorporated 2023
Share capital NOK 30,000

Signals

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

HAPPYHOUR AS is registered as a limited company in Bærum, Akershus with organisation number 831189452. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 300000 shares. The company's stated purpose is: “Investere i verdipapirer og hva som står i naturlig forbindelse.”.

Key figures · 2025

Operating profit
NOK −915
▲ +20 %
Equity
NOK 22,000
▼ −4 %
Est. value
NOK 26,000

Financial health · 2025

Liquidity
0.02
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
5.5%
Weak
Equity as a share of total capital

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

Who owns HAPPYHOUR AS?

HAPPYHOUR AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about HAPPYHOUR AS

Who owns HAPPYHOUR AS?

LARS BERGE ANDERSEN is the largest registered owner, with 33.3%.

Where is HAPPYHOUR AS based?

HAPPYHOUR AS has its business address in Lysaker.

Property

Business address Fornebuveien 40, 1366 Lysaker
Cadastral unit 3201-41/68/0/0
Building Kontor- og administrasjonsbygning, rådhus · 1 unit

20 companies are registered at this address.

The address this company is registered at, from the company register and matched against the cadastre. It does not say who owns the property — a company may be a tenant, and the address is often its accountant's. Source: Brønnøysundregistrene and © Kartverket.

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

Report a problem

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