BIZTRAC BETA
Rental and leasing of other machinery, equipment and tangible goods n.e.c.

INTERLOG AS

Org. no. 917102864 Limited company (AS) Nittedal Incorporated 2016 Active
Ownership graph ↗
Revenue 2025 NOK 1.4m
Operating profit NOK 493,000
Equity NOK −86,000
Incorporated 2016
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−86k kr).
  • Nylig endring 2026-05-20 Adresseendring registrert 2026-05-20.

INTERLOG AS is registered as a limited company in Nittedal, Akershus with organisation number 917102864. The business is classified under rental and leasing of other machinery, equipment and tangible goods n.e.c. (NACE 77.390). The company was incorporated in 2016. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Utleie av containere og utstyr, tilby logistikktjenester, samt det som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.4m in revenue and NOK 493,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.4m
Operating profit
NOK 493,000
Equity
NOK −86,000
Est. value
NOK 2.3m

Financial health · 2025

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

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

Who owns INTERLOG AS?

NITTEDAL HOLDING AS
INTERLOG AS
NOK 1.4m rev. · NOK 493,000 profit

INTERLOG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about INTERLOG AS

Who owns INTERLOG AS?

NITTEDAL HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of INTERLOG AS?

INTERLOG AS had revenue of NOK 1.4m in 2025.

Where is INTERLOG AS based?

INTERLOG AS has its business address in Hagan.

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.