BIZTRAC BETA
Uoppgitt

TK MULLIGAN AS

Org. no. 934391861 Limited company (AS) Bergen Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 315,000
Operating profit NOK −72,000
Equity NOK −41,000
Incorporated 2024
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−41k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−72k kr).

TK MULLIGAN AS is registered as a limited company in Bergen, Vestland with organisation number 934391861. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Investeringsvirksomhet, herunder kjøp, salg, eie og forvalte aksjer eller andre former for eierskap, samt delta som långivere og garantister i andre selskaper, samt alt som hører naturlig inn under dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 315,000 in revenue and NOK −72,000 in operating profit.

Key figures · 2025

Revenue
NOK 315,000
Operating profit
NOK −72,000
Equity
NOK −41,000

Financial health · 2025

Liquidity
68.02
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-1.4%
Weak
Equity as a share of total capital

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

Who owns TK MULLIGAN AS?

NYSTAD SHIPPING AS
TK MULLIGAN AS
NOK 315,000 rev. · NOK −72,000 profit

TK MULLIGAN AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about TK MULLIGAN AS

Who owns TK MULLIGAN AS?

NYSTAD SHIPPING AS is the largest registered owner, with 50.0%.

What is the revenue of TK MULLIGAN AS?

TK MULLIGAN AS had revenue of NOK 315,000 in 2025.

Where is TK MULLIGAN AS based?

TK MULLIGAN AS has its business address in Straumsgrend.

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.