biztrac. BETA
COMPANY REGISTER PROFILE
887988692 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Construction of residential and non-residential buildings

TOTOMMFIRE DA

Org. no. 887988692 General partnership with shared liability (DA) Vestby Incorporated 2005 Active
Ownership graph ↗
Revenue 2025 NOK 257,000
Operating profit NOK −155,000
Equity NOK 18,000
Incorporated 2005

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−155k kr).

TOTOMMFIRE DA is registered as a general partnership with shared liability in Vestby, Akershus with organisation number 887988692. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2005. The company's stated purpose is: “Håndtverkstjenester innenfor byggfaget, investeringer i fast eiendom og utleie.”. The most recent filed accounts, for the 2025 financial year, show NOK 257,000 in revenue and NOK −155,000 in operating profit.

Key figures · 2025

Revenue
NOK 257,000
▼ −27 %
Operating profit
NOK −155,000
▼ −189 %
Equity
NOK 18,000
▼ −89 %
Est. value
NOK 97,000

Financial health · 2025

Liquidity
1.28
Satisfactory
Current assets ÷ current liabilities
Profitability
–
Not available
Return on total assets
Solidity
21.6%
Weak
Equity as a share of total capital

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

Who owns TOTOMMFIRE DA?

No shareholders are registered for TOTOMMFIRE DA in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about TOTOMMFIRE DA

What is the revenue of TOTOMMFIRE DA?

TOTOMMFIRE DA had revenue of NOK 257,000 in 2025.

Who is the general manager of TOTOMMFIRE DA?

Viggo Slang is registered as general manager of TOTOMMFIRE DA.

Where is TOTOMMFIRE DA based?

TOTOMMFIRE DA has its business address in Hølen.

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.