BIZTRAC BETA
Rental and operating of own or leased real estate

BROGATEN 17 AS

Org. no. 930818070 Limited company (AS) Flekkefjord Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 431,000
Operating profit NOK 326,000
Equity NOK 1.6m
Incorporated 2023
Share capital NOK 300,000

BROGATEN 17 AS is registered as a limited company in Flekkefjord, Agder with organisation number 930818070. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2023. Registered share capital is NOK 300,000, divided into 3000 shares. The company's stated purpose is: “Kjøpe, selge, eie, leie ut, utvikle og drifte fast eiendom, herunder å delta i andre selskap med lignende virksomhet, og kjøp og salg av aksjer eller på annen måte gjøre seg interessert i andre foretak.”. The most recent filed accounts, for the 2025 financial year, show NOK 431,000 in revenue and NOK 326,000 in operating profit.

Key figures · 2025

Revenue
NOK 431,000
Operating profit
NOK 326,000
Equity
NOK 1.6m
Est. value
NOK 1.7m

Financial health · 2025

Liquidity
0.88
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
26.5%
Good
Equity as a share of total capital

Who owns BROGATEN 17 AS?

CHARLOTTE TANGVALD LARSEN
BROGATEN 17 AS
NOK 431,000 rev. · NOK 326,000 profit

BROGATEN 17 AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about BROGATEN 17 AS

Who owns BROGATEN 17 AS?

CHARLOTTE TANGVALD LARSEN is the largest registered owner, with 33.3%.

What is the revenue of BROGATEN 17 AS?

BROGATEN 17 AS had revenue of NOK 431,000 in 2025.

Who is the general manager of BROGATEN 17 AS?

Charlotte Tangvald Larsen is registered as general manager of BROGATEN 17 AS.

Where is BROGATEN 17 AS based?

BROGATEN 17 AS has its business address in Flekkefjord.

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.