biztrac. BETA
COMPANY REGISTER PROFILE
931715240 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Silviculture and other forestry activities

MILI SKOGSERVICE AS

Org. no. 931715240 Limited company (AS) Drammen Incorporated 2023 Active
Revenue 2025 NOK 10.3m
Operating profit NOK 1.0m
Equity NOK 849,000
Incorporated 2023
Employees 36
Share capital NOK 30,000

MILI SKOGSERVICE AS is registered as a limited company in Drammen, Buskerud with organisation number 931715240. The business is classified under silviculture and other forestry activities (NACE 02.100). The company was incorporated in 2023 and has 36 registered employees. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Tjenester relatert til skogsdrift, samt alt hva hermed står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 10.3m in revenue and NOK 1.0m in operating profit.

Key figures · 2025

Revenue
NOK 10.3m
▲ +60 %
Operating profit
NOK 1.0m
▲ +370 %
Equity
NOK 849,000
▲ +1008 %
Est. value
NOK 3.4m

Financial health · 2025

Liquidity
1.73
Good
Current assets ÷ current liabilities
Profitability
85.1%
Very good
Return on total assets
Solidity
55.2%
Very good
Equity as a share of total capital

Who owns MILI SKOGSERVICE AS?

MILI SKOGSERVICE AS
NOK 10.3m rev. · NOK 1.0m profit

MILI SKOGSERVICE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about MILI SKOGSERVICE AS

Who owns MILI SKOGSERVICE AS?

Srdjan Milic is the largest registered owner, with 100.0%.

What is the revenue of MILI SKOGSERVICE AS?

MILI SKOGSERVICE AS had revenue of NOK 10.3m in 2025.

Who is the general manager of MILI SKOGSERVICE AS?

Srdjan Milic is registered as general manager of MILI SKOGSERVICE AS.

Where is MILI SKOGSERVICE AS based?

MILI SKOGSERVICE AS has its business address in Mjøndalen.

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.