biztrac. BETA
COMPANY REGISTER PROFILE
931469304 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Development of building projects

BROGATEN 25 AS

Org. no. 931469304 Limited company (AS) Flekkefjord Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 14,000
Operating profit NOK 2,000
Equity NOK −493,000
Incorporated 2023
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−493k kr).

BROGATEN 25 AS is registered as a limited company in Flekkefjord, Agder with organisation number 931469304. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 120 shares. The company's stated purpose is: “Eiendomsutvikling og det som naturlig hører sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 14,000 in revenue and NOK 2,000 in operating profit.

Key figures · 2025

Revenue
NOK 14,000
▼ −74 %
Operating profit
NOK 2,000
▼ −95 %
Equity
NOK −493,000
▼ −102 %
Est. value
NOK 81,000

Financial health · 2025

Liquidity
26.06
Very good
Current assets ÷ current liabilities
Profitability
0.7%
Not satisfactory
Return on total assets
Solidity
-11.3%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns BROGATEN 25 AS?

BROGATEN 25 AS has 5 registered shareholders:

All shareholders and roles →

Frequently asked questions about BROGATEN 25 AS

Who owns BROGATEN 25 AS?

Jan Kåre Hansen is the largest registered owner, with 20.0%.

What is the revenue of BROGATEN 25 AS?

BROGATEN 25 AS had revenue of NOK 14,000 in 2025.

Who is the general manager of BROGATEN 25 AS?

Tor-Sverre Hansen is registered as general manager of BROGATEN 25 AS.

Where is BROGATEN 25 AS based?

BROGATEN 25 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 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.