BIZTRAC BETA
Computer consultancy and computer facilities management activities

LAG3 AS

Org. no. 835219402 Limited company (AS) Nordre Follo Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −9,000
Equity NOK 14,000
Incorporated 2025
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−9k kr).

LAG3 AS is registered as a limited company in Nordre Follo, Akershus with organisation number 835219402. The business is classified under computer consultancy and computer facilities management activities (NACE 62.200). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Selge varer og tjenester innen IT og annet som naturlig sammenfaller med dette, samt deltakelse i andre selskaper, investeringer og nærliggende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −9,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −9,000
Equity
NOK 14,000
Est. value
NOK 26,000

Financial health · 2025

Liquidity
Not available
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
100.0%
Weak
Equity as a share of total capital

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

Who owns LAG3 AS?

MARTIN THORESEN KARLSEN
LAG3 AS
NOK 0 rev. · NOK −9,000 profit

LAG3 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LAG3 AS

Who owns LAG3 AS?

MARTIN THORESEN KARLSEN is the largest registered owner, with 100.0%.

What is the revenue of LAG3 AS?

LAG3 AS had revenue of NOK 0 in 2025.

Who is the general manager of LAG3 AS?

Martin Thoresen Karlsen is registered as general manager of LAG3 AS.

Where is LAG3 AS based?

LAG3 AS has its business address in Ski.

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.