BIZTRAC BETA
Interior design activities

HAGEN OG BRYHN AS

Org. no. 919751711 Limited company (AS) Oslo Incorporated 2017 Active
Ownership graph ↗
Revenue 2024 NOK 3.2m
Operating profit NOK 275,000
Equity NOK 341,000
Incorporated 2017
Employees 5
Share capital NOK 30,000

HAGEN OG BRYHN AS is registered as a limited company in Oslo, Oslo with organisation number 919751711. The business is classified under interior design activities (NACE 74.130). The company was incorporated in 2017 and has 5 registered employees. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Utføring av boligstyling og interiørdesign. Boligstyling: Styling av leiligheter for salg. Interiørdesign: For bedrifter eller privatpersoner, interiørkonsultasjon og rådgivning. Og andre tjenester som naturlig hører sammen med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 3.2m in revenue and NOK 275,000 in operating profit.

Key figures · 2024

Revenue
NOK 3.2m
Operating profit
NOK 275,000
Equity
NOK 341,000
Est. value
NOK 1.5m

Financial health · 2024

Liquidity
1.31
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
35.2%
Good
Equity as a share of total capital

Who owns HAGEN OG BRYHN AS?

BENEDIKTE BRYHN
HAGEN OG BRYHN AS
NOK 3.2m rev. · NOK 275,000 profit

HAGEN OG BRYHN AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about HAGEN OG BRYHN AS

Who owns HAGEN OG BRYHN AS?

BENEDIKTE BRYHN is the largest registered owner, with 40.0%.

What is the revenue of HAGEN OG BRYHN AS?

HAGEN OG BRYHN AS had revenue of NOK 3.2m in 2024.

Who is the general manager of HAGEN OG BRYHN AS?

Ane Hagen is registered as general manager of HAGEN OG BRYHN AS.

Where is HAGEN OG BRYHN AS based?

HAGEN OG BRYHN 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.