BIZTRAC BETA
Computer programming activities

FRIENDLY TECH AS

Org. no. 936629482 Limited company (AS) Nesodden Incorporated 2025 Active
Ownership graph ↗
Revenue NOK 0
Operating profit NOK −4,000
Equity NOK 18,000
Incorporated 2025
Share capital NOK 30,000

Signals

3 flags
  • Driftsunderskudd Siste driftsresultat er negativt (−4k kr).
  • Mangler regnskap Ingen årsregnskap er registrert for selskapet.
  • Nystiftet selskap Selskapet ble stiftet 2025-10-27.

FRIENDLY TECH AS is registered as a limited company in Nesodden, Akershus with organisation number 936629482. The business is classified under computer programming activities (NACE 62.100). 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 programvare og annet som naturlig sammenfaller med dette, samt deltakelse i andre selskaper, investeringer og nærliggende virksomhet.”.

Key figures

Revenue
NOK 0
Operating profit
NOK −4,000
Equity
NOK 18,000
Est. value
NOK 33,000

Financial health · 2025

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

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

Who owns FRIENDLY TECH AS?

FASILO AS
FRIENDLY TECH AS
NOK 0 rev. · NOK −4,000 profit

FRIENDLY TECH AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about FRIENDLY TECH AS

Who owns FRIENDLY TECH AS?

FASILO AS is the largest registered owner, with 100.0%.

What is the revenue of FRIENDLY TECH AS?

FRIENDLY TECH AS had revenue of NOK 0.

Who is the general manager of FRIENDLY TECH AS?

Greger Flak is registered as general manager of FRIENDLY TECH AS.

Where is FRIENDLY TECH AS based?

FRIENDLY TECH AS has its business address in Nesodden.

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.