BIZTRAC BETA
Other telecommunication activities

MOBINO AS

Org. no. 936570658 Limited company (AS) Fredrikstad Incorporated 2025 Active
Ownership graph ↗
Incorporated 2025
Share capital NOK 2.0m
75
Credit score
Meget lav risiko
Operating margin
0.0%
Net margin
0.0%
Equity ratio
100.0%
Current ratio
0.00
Debt ratio
0.00
Audit
Not audited

Analysis

  • Selskapet har en god egenkapitalandel på 100.0%.
  • Kortsiktig gjeld overstiger omløpsmidlene – negativ likviditetsgrad.
  • Selskapet har ingen langsiktig gjeld.

Income statement

Periode: 2025-01-01 – 2025-12-31 · Alle tall i NOK

Total operating revenueNOK 0
Total operating costsNOK 0
Operating profit (EBIT)NOK 0
Net financial itemsNOK 0
Profit before taxNOK 0
Profit for the yearNOK 0

Balance sheet

Per 2025-12-31 · Alle tall i NOK

Assets

Non-current assetsNOK 0
Current assetsNOK 24,000
Total assetsNOK 24,000

Equity and liabilities

Paid-in equityNOK 24,000
Retained earningsNOK 0
Total equityNOK 24,000
Current liabilitiesNOK 0
Non-current liabilitiesNOK 0
Total equity and liabilitiesNOK 24,000

Full financial statements

Financial year 2025 · NOK · read automatically from the filed annual report

Income statement

2025Previous year
ÅrsresultatNOK 0NOK 0
Utskriftedato 25.06.2026NOK 936.6m

Balance sheet

2025Previous year
Andre kortsiktige fordringerNOK 24,000
Sum fordringerNOK 24,000
Sum omløpsmidlerNOK 24,000
Sum eiendelerNOK 24,000NOK 0
AksjekapitalNOK 30,000
Annen innskutt egenkapitalNOK −7,000
Sum innskutt egenkapitalNOK 24,000
Sum egenkapitalNOK 24,000
Sum gjeld SOM EGENKAPITAL OG GJELDNOK 24,000NOK 0
Utskriftedato 25.06.2026NOK 936.6m

The figures are read automatically from the filed annual report and may contain errors. Control figures are reconciled against the Register of Company Accounts.

Source: the Brønnøysund registers / the Register of Company Accounts. Credit score calculated by Biztrac.

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.