BIZTRAC BETA
Accounting and bookkeeping

247REGNSKAP AS

Org. no. 913168038 Limited company (AS) Kristiansund Incorporated 2014 Active
Ownership graph ↗
Revenue 2024 NOK 3.2m
Operating profit NOK 35,000
Equity NOK 209,000
Incorporated 2014
Share capital NOK 100,000

247REGNSKAP AS is registered as a limited company in Kristiansund, Møre og Romsdal with organisation number 913168038. The business is classified under accounting and bookkeeping (NACE 69.202). The company was incorporated in 2014. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Å tilby tjenester innenfor økonomi, regnskap og administrasjon for eksterne selskap, og alt som naturlig faller sammen med dette, herunder å delta i andre selskaper med lignende virksomhet, kjøp og salg av aksjer, eller på annen måte gjøre seg interessert i andre foretagender.”. The most recent filed accounts, for the 2024 financial year, show NOK 3.2m in revenue and NOK 35,000 in operating profit.

Key figures · 2024

Revenue
NOK 3.2m
Operating profit
NOK 35,000
Equity
NOK 209,000
Est. value
NOK 338,000

Financial health · 2024

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

Who owns 247REGNSKAP AS?

WM EIENDOM AS
247REGNSKAP AS
NOK 3.2m rev. · NOK 35,000 profit

247REGNSKAP AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about 247REGNSKAP AS

Who owns 247REGNSKAP AS?

WM EIENDOM AS is the largest registered owner, with 100.0%.

What is the revenue of 247REGNSKAP AS?

247REGNSKAP AS had revenue of NOK 3.2m in 2024.

Who is the general manager of 247REGNSKAP AS?

Geir Rakvåg Nelvik is registered as general manager of 247REGNSKAP AS.

Where is 247REGNSKAP AS based?

247REGNSKAP AS has its business address in Kristiansund N.

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.