BIZTRAC BETA
Manufacture of beer

YOU ARE A FUNNY MAN AS

Org. no. 920466567 Limited company (AS) Oslo Incorporated 2018 Active
Ownership graph ↗
Revenue 2025 NOK 7.3m
Operating profit NOK 4,000
Equity NOK 1.0m
Incorporated 2018
Employees 8
Share capital NOK 130,000

YOU ARE A FUNNY MAN AS is registered as a limited company in Oslo, Oslo with organisation number 920466567. The business is classified under manufacture of beer (NACE 11.050). The company was incorporated in 2018 and has 8 registered employees. Registered share capital is NOK 130,000, divided into 130000 shares. The company's stated purpose is: “Drift av serveringssted med salg og servering av mat og drikke, herunder alkoholholdige drikkevarer i henhold til gjeldende lover og forskrifter.”. The most recent filed accounts, for the 2025 financial year, show NOK 7.3m in revenue and NOK 4,000 in operating profit.

Key figures · 2025

Revenue
NOK 7.3m
Operating profit
NOK 4,000
Equity
NOK 1.0m
Est. value
NOK 547,000

Financial health · 2025

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

Who owns YOU ARE A FUNNY MAN AS?

CRAFT BEER BAR HOLDING APS
YOU ARE A FUNNY MAN AS
NOK 7.3m rev. · NOK 4,000 profit

YOU ARE A FUNNY MAN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about YOU ARE A FUNNY MAN AS

Who owns YOU ARE A FUNNY MAN AS?

CRAFT BEER BAR HOLDING APS is the largest registered owner, with 100.0%.

What is the revenue of YOU ARE A FUNNY MAN AS?

YOU ARE A FUNNY MAN AS had revenue of NOK 7.3m in 2025.

Who is the general manager of YOU ARE A FUNNY MAN AS?

Noel David Heath is registered as general manager of YOU ARE A FUNNY MAN AS.

Where is YOU ARE A FUNNY MAN AS based?

YOU ARE A FUNNY MAN AS has its business address in Oslo.

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.