biztrac. BETA
COMPANY REGISTER PROFILE
814156192 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Sports and recreation education

FOLLO AKTIV AS

Org. no. 814156192 Limited company (AS) Oslo Incorporated 2014 Active
Revenue 2025 NOK 158,000
Operating profit NOK −107,000
Equity NOK 660,000
Incorporated 2014
Share capital NOK 30,000

Signals

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

FOLLO AKTIV AS is registered as a limited company in Oslo, Oslo with organisation number 814156192. The business is classified under sports and recreation education (NACE 85.510). The company was incorporated in 2014. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Instruksjon, trening og helse og andre produkter/tjenester som naturlig hører sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 158,000 in revenue and NOK −107,000 in operating profit.

Key figures · 2025

Revenue
NOK 158,000
▼ −57 %
Operating profit
NOK −107,000
▲ +52 %
Equity
NOK 660,000
▲ +6 %
Est. value
NOK 577,000

Financial health · 2025

Liquidity
7.04
Very good
Current assets ÷ current liabilities
Profitability
5.5%
Weak
Return on total assets
Solidity
85.8%
Very good
Equity as a share of total capital

Who owns FOLLO AKTIV AS?

FOLLO AKTIV AS
NOK 158,000 rev. · NOK −107,000 profit

FOLLO AKTIV AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about FOLLO AKTIV AS

Who owns FOLLO AKTIV AS?

Tommie Berkani is the largest registered owner, with 100.0%.

What is the revenue of FOLLO AKTIV AS?

FOLLO AKTIV AS had revenue of NOK 158,000 in 2025.

Who is the general manager of FOLLO AKTIV AS?

Tommie Berkani is registered as general manager of FOLLO AKTIV AS.

Where is FOLLO AKTIV AS based?

FOLLO AKTIV AS has its business address in Oslo.

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.