biztrac. BETA
COMPANY REGISTER PROFILE
929065492 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Rental and operating of own or leased real estate

MILLIGAN INVEST AS

Org. no. 929065492 Limited company (AS) Flekkefjord Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 955,000
Operating profit NOK 18,000
Equity NOK 2.2m
Incorporated 2022
Share capital NOK 1.1m

MILLIGAN INVEST AS is registered as a limited company in Flekkefjord, Agder with organisation number 929065492. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2022. Registered share capital is NOK 1.1m, divided into 30000 shares. The company's stated purpose is: “Utleie og eiendomsinvesteringer.”. The most recent filed accounts, for the 2025 financial year, show NOK 955,000 in revenue and NOK 18,000 in operating profit.

Key figures · 2025

Revenue
NOK 955,000
▼ −10 %
Operating profit
NOK 18,000
▼ −97 %
Equity
NOK 2.2m
▼ −21 %
Est. value
NOK 2.0m

Financial health · 2025

Liquidity
1.46
Satisfactory
Current assets ÷ current liabilities
Profitability
0.3%
Not satisfactory
Return on total assets
Solidity
17.5%
Satisfactory
Equity as a share of total capital

Who owns MILLIGAN INVEST AS?

MILLIGAN INVEST AS
NOK 955,000 rev. · NOK 18,000 profit

MILLIGAN INVEST AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about MILLIGAN INVEST AS

Who owns MILLIGAN INVEST AS?

Kristoffer Milligan is the largest registered owner, with 100.0%.

What is the revenue of MILLIGAN INVEST AS?

MILLIGAN INVEST AS had revenue of NOK 955,000 in 2025.

Who is the general manager of MILLIGAN INVEST AS?

Kristoffer Milligan is registered as general manager of MILLIGAN INVEST AS.

Where is MILLIGAN INVEST AS based?

MILLIGAN INVEST 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.