BIZTRAC BETA
Construction of residential and non-residential buildings

EFFEKTIV AS

Org. no. 920929362 Limited company (AS) Grimstad Incorporated 2018 Active
Ownership graph ↗
Revenue 2024 NOK 46,000
Operating profit NOK 31,000
Equity NOK −21,000
Incorporated 2018
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−21k kr).

EFFEKTIV AS is registered as a limited company in Grimstad, Agder with organisation number 920929362. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2018. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Å drive entreprenørvirksomhet, handelsvirksomhet, eiendomsdrift og hva dermed står i forbindelse. Selskapet kan også gjennom aksjerverv eller på annen måte delta i eller gjøre seg interessert i annen virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 46,000 in revenue and NOK 31,000 in operating profit.

Key figures · 2024

Revenue
NOK 46,000
Operating profit
NOK 31,000
Equity
NOK −21,000
Est. value
NOK 155,000

Financial health · 2025

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

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

Who owns EFFEKTIV AS?

ANDERS WILLY PEDERSEN
EFFEKTIV AS
NOK 46,000 rev. · NOK 31,000 profit

EFFEKTIV AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about EFFEKTIV AS

Who owns EFFEKTIV AS?

ANDERS WILLY PEDERSEN is the largest registered owner, with 100.0%.

What is the revenue of EFFEKTIV AS?

EFFEKTIV AS had revenue of NOK 46,000 in 2024.

Where is EFFEKTIV AS based?

EFFEKTIV AS has its business address in Fevik.

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.