BIZTRAC BETA
Retail sale of footwear and leather goods

BAG BYHAVEN AS

Org. no. 975964752 Limited company (AS) Trondheim Incorporated 1995 Active
Ownership graph ↗
Revenue 2024 NOK 8.9m
Operating profit NOK 616,000
Equity NOK 630,000
Incorporated 1995
Employees 7
Share capital NOK 100,000

BAG BYHAVEN AS is registered as a limited company in Trondheim, Trøndelag with organisation number 975964752. The business is classified under retail sale of footwear and leather goods (NACE 47.720). The company was incorporated in 1995 and has 7 registered employees. Registered share capital is NOK 100,000, divided into 50 shares. The company's stated purpose is: “Kjøp og salg av lærvarer og alt som står i forbindelse, herunder delta i andre selskaper med lignende virksomheter.”. The most recent filed accounts, for the 2024 financial year, show NOK 8.9m in revenue and NOK 616,000 in operating profit.

Key figures · 2024

Revenue
NOK 8.9m
Operating profit
NOK 616,000
Equity
NOK 630,000
Est. value
NOK 2.7m

Financial health · 2024

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

Who owns BAG BYHAVEN AS?

AAGAARD HOLDING AS
BAG BYHAVEN AS
NOK 8.9m rev. · NOK 616,000 profit

BAG BYHAVEN AS has 1 registered shareholder:

All shareholders and roles →

Group structure

BAG BYHAVEN AS er morselskap for 7 datterselskaper:

Frequently asked questions about BAG BYHAVEN AS

Who owns BAG BYHAVEN AS?

AAGAARD HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of BAG BYHAVEN AS?

BAG BYHAVEN AS had revenue of NOK 8.9m in 2024.

Who is the general manager of BAG BYHAVEN AS?

Martin Aagaard is registered as general manager of BAG BYHAVEN AS.

Where is BAG BYHAVEN AS based?

BAG BYHAVEN AS has its business address in Trondheim.

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.