BIZTRAC BETA
Activities of advertising agencies

FIRES AS

Org. no. 927135299 Limited company (AS) Bærum Incorporated 2021 Active
Ownership graph ↗
Revenue 2024 NOK 89,000
Operating profit NOK −206,000
Equity NOK 481,000
Incorporated 2021
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−206k kr).

FIRES AS is registered as a limited company in Bærum, Akershus with organisation number 927135299. The business is classified under activities of advertising agencies (NACE 73.110). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Handel og andre produkter/tjenester som naturlig hører sammen med dette, herunder å delta i andre selskap med lignende virksomhet, og investeringer i fast eiendom, 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 2024 financial year, show NOK 89,000 in revenue and NOK −206,000 in operating profit.

Key figures · 2024

Revenue
NOK 89,000
Operating profit
NOK −206,000
Equity
NOK 481,000
Est. value
NOK 328,000

Financial health · 2024

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

Who owns FIRES AS?

THOMAS HÅKONSEN
FIRES AS
NOK 89,000 rev. · NOK −206,000 profit

FIRES AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about FIRES AS

Who owns FIRES AS?

THOMAS HÅKONSEN is the largest registered owner, with 100.0%.

What is the revenue of FIRES AS?

FIRES AS had revenue of NOK 89,000 in 2024.

Who is the general manager of FIRES AS?

Thomas Håkonsen is registered as general manager of FIRES AS.

Where is FIRES AS based?

FIRES AS has its business address in Haslum.

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.