BIZTRAC BETA
Development of building projects

HAPPY TIME EIENDOM AS

Org. no. 916227183 Limited company (AS) Grimstad Incorporated 2015 Active
Ownership graph ↗
Revenue 2025 NOK 1.8m
Operating profit NOK 1.2m
Equity NOK 1.6m
Incorporated 2015
Share capital NOK 30,000

HAPPY TIME EIENDOM AS is registered as a limited company in Grimstad, Agder with organisation number 916227183. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2015. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Eiendomsutvikling, reparasjon, vedlikehold og utleie av bygg, samt annen virksomhet som naturlig hører sammen med dette. Investering i aksjer, andeler og andre verdipapirer.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.8m in revenue and NOK 1.2m in operating profit.

Key figures · 2025

Revenue
NOK 1.8m
Operating profit
NOK 1.2m
Equity
NOK 1.6m
Est. value
NOK 3.7m

Financial health · 2025

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

Who owns HAPPY TIME EIENDOM AS?

HAPPY TIME PIZZERIA AS
HAPPY TIME EIENDOM AS
NOK 1.8m rev. · NOK 1.2m profit

HAPPY TIME EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about HAPPY TIME EIENDOM AS

Who owns HAPPY TIME EIENDOM AS?

HAPPY TIME PIZZERIA AS is the largest registered owner, with 100.0%.

What is the revenue of HAPPY TIME EIENDOM AS?

HAPPY TIME EIENDOM AS had revenue of NOK 1.8m in 2025.

Who is the general manager of HAPPY TIME EIENDOM AS?

Walid Yonan Abraham is registered as general manager of HAPPY TIME EIENDOM AS.

Where is HAPPY TIME EIENDOM AS based?

HAPPY TIME EIENDOM AS has its business address in Grimstad.

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.