BIZTRAC BETA
Accounting and bookkeeping

FRANKS REGNSKAP AS

Org. no. 934137833 Limited company (AS) Lindesnes Incorporated 2024 Active
Ownership graph ↗
Revenue 2024 NOK 419,000
Operating profit NOK 68,000
Equity NOK 103,000
Incorporated 2024
Employees 6
Share capital NOK 50,000

FRANKS REGNSKAP AS is registered as a limited company in Lindesnes, Agder with organisation number 934137833. The business is classified under accounting and bookkeeping (NACE 69.202). The company was incorporated in 2024 and has 6 registered employees. Registered share capital is NOK 50,000, divided into 50000 shares. The company's stated purpose is: “Regnskapstjenester og tilhørende rådgivning samt alt som naturlig hører sammen med dette, herunder gjennom aksjetegning eller på annen måte delta i andre selskap med lignende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 419,000 in revenue and NOK 68,000 in operating profit.

Key figures · 2024

Revenue
NOK 419,000
Operating profit
NOK 68,000
Equity
NOK 103,000
Est. value
NOK 378,000

Financial health · 2024

Liquidity
1.34
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
25.3%
Good
Equity as a share of total capital

Who owns FRANKS REGNSKAP AS?

FRANK OLSEN
FRANKS REGNSKAP AS
NOK 419,000 rev. · NOK 68,000 profit

FRANKS REGNSKAP AS has 1 registered shareholder:

All shareholders and roles →

Which companies does FRANKS REGNSKAP AS own?

FRANKS REGNSKAP AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about FRANKS REGNSKAP AS

Who owns FRANKS REGNSKAP AS?

FRANK OLSEN is the largest registered owner, with 100.0%.

What is the revenue of FRANKS REGNSKAP AS?

FRANKS REGNSKAP AS had revenue of NOK 419,000 in 2024.

Where is FRANKS REGNSKAP AS based?

FRANKS REGNSKAP AS has its business address in Lindesnes.

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.